Authentication Issue - New Prompt Screen before login screen

[xjcarter]

Hi All-
Looks like IBRK has added a new prompt screen that is impeding my login process.
Here is the high level description of what I believe is happening:

1. Now have mobile authenticate enabled through in IBRK Mobile app.
2. As a result - I am now getting a prompt screen (image attached) asking me to go to my mobile app and do my authentication there.
3. I have a little authentication server setup to take my old SMS authentication code and feed them to IBeam - to complete the automated login (which had been working great until this week). My logs verify that SMS message is not being posted to my server so that IBeam can request it.

Therefore my question is:

1. How do I disable the IBRK Mobile 2FA (I thought I HAD to activate this to get in to my account ) and get back to the old handshaking via SMS? IBRK documentation hints that this functionality exists in emergency cases:
   " IBKR also offers temporary two-factor authentication methods if your device is lost, offline or otherwise unavailable.

   SMS Authentication

    If you have not yet configured IBKR Mobile or received a Digital Security Card+, you can request that an authentication code be sent to your mobile device via SMS (text) message. This code must be entered in the login window to complete the login process.
   

"

How do I revert back? I surely don't want to be going through the mobile app for authentication.

Thanks for any and all help!

[Voyz]

Hey @xjcarter sorry to hear this has happened. IBKR support says that SMS is deprecated and they are not letting anyone switch back to it. You may want to reach them and try your luck, as I don't know of any manual way of setting it ourselves in the settings

[xjcarter]

thanks guys! yeah- I'll try some smooth talking ;)

…

On Mon, Oct 13, 2025 at 9:28 AM voyz ***@***.***> wrote: *Voyz* left a comment (Voyz/ibeam#263) <#263 (comment)> Hey @xjcarter <https://github.com/xjcarter> sorry to hear this has happened. IBKR support says that SMS is deprecated and they are not letting anyone switch back to it. You may want to reach them and try your luck, as I don't know of any manual way of setting it ourselves in the settings — Reply to this email directly, view it on GitHub <#263 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADMDCZY3TIAU6Q4MPLHA5DL3XOSITAVCNFSM6AAAAACI3OAZSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJXGUZTQMRVGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mbruni]

Any luck @xjcarter ?

[xjcarter]

I didn't have the time the last couple of days to address the issue. I'll circle back with my findings tomorrow. Fingers crossed!

…

On Thu, Oct 16, 2025 at 3:14 PM Mike Bruni ***@***.***> wrote: *mbruni* left a comment (Voyz/ibeam#263) <#263 (comment)> Any luck @xjcarter <https://github.com/xjcarter> ? — Reply to this email directly, view it on GitHub <#263 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADMDCZ2VXB5M54EH5C4YRXL3X7VAPAVCNFSM6AAAAACI3OAZSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJSGQ4TKOJRGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[michaeljherrmann]

@xjcarter it perhaps sounds like you accidentally enabled IBKey? For a while, I was in a similar situation and built another solution here (if you're interested). But since IBKR recently added support for TOTP (like Google Auth), I would suggest switching to that if you can. It's much easier and more reliable for automating the login.

[Voyz]

To add some context on @michaeljherrmann's answer and solution:

While it's really awesome you managed to do this without any kind of browser and emulation - I'm genuinely impressed you figured out how to do it - I recall several such attempts in the past, and usually the conversation stopped when discussing whether doing so would be against IBKR terms of service with some voices raised that such direct interaction with the API could get one into trouble.

I just suggest to be wary of the TOCs to avoid having any issues with access to your account. If it wasn't for that, I'd recommend that solution over what IBeam does - it's clearly more elegant.

[xjcarter]

Thanks Michael- Yeah- I have been in contact with the API integration team over at IBRK and they are helping me get set up with OAuth2.0 authentication. I just had to generate a public key for them and go through their registration process (it's simply opening a new service ticket- and then having them approve it) After all that is set- I believe they will ship over some sample code to complete the set up. I'll keep everyone posted!

…

On Sat, Nov 1, 2025 at 6:27 AM Michael Herrmann ***@***.***> wrote: *michaeljherrmann* left a comment (Voyz/ibeam#263) <#263 (comment)> @xjcarter <https://github.com/xjcarter> it perhaps sounds like you accidentally enabled IBKey? For a while, I was in a similar situation and built another solution here <https://github.com/michaeljherrmann/ib-gateway-service?tab=readme-ov-file#deprecated-authentication-methods> (if you're interested). But since IBKR recently added support for TOTP (like Google Auth), I would suggest switching to that if you can. It's much easier and more reliable for automating the login. — Reply to this email directly, view it on GitHub <#263 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADMDCZ4D6ANBQIMFJU5UKTL32SDIHAVCNFSM6AAAAACI3OAZSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINZWGE2TGMRRHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jefag]

I'm coincidentally just trying out IBeam for the first time, today, and was super confused -- presumably I'm hitting the same blocker, as I too have the mobile prompt. For users that don't mind hitting the approve on their mobile any time they are prompted, is there a patch that would work?

The logs are confusing, because I see Webpage displayed "Client login succeeds" and Logging in succeeded but then Repeatedly reauthenticating failed 3 times. Killing the Gateway...

ibeam  | 2025-11-02 14:14:48,143|I| Gateway connection established
ibeam  | 2025-11-02 14:14:48,240|I| NO SESSION Status(running=True, session=False, connected=False, authenticated=False, competing=False, collision=False, session_id=None, server_name=None, server_version=None, expires=None)
ibeam  | 2025-11-02 14:14:48,240|I| Authentication strategy: "B"
ibeam  | 2025-11-02 14:14:48,240|I| No active sessions, logging in...
ibeam  | 2025-11-02 14:14:48,240|I| Loading auth webpage at https://localhost:5000/sso/Login?forwardTo=22&RL=1&ip2loc=on
ibeam  | 2025-11-02 14:14:54,881|I| Gateway auth webpage loaded
ibeam  | 2025-11-02 14:14:54,881|I| Login attempt number 1
ibeam  | 2025-11-02 14:15:00,060|I| Submitting the form
ibeam  | 2025-11-02 14:15:09,899|I| Webpage displayed "Client login succeeds"
ibeam  | 2025-11-02 14:15:10,900|I| Cleaning up the resources. Display: <pyvirtualdisplay.display.Display object at 0xffff7fa64490> | Driver: <selenium.webdriver.chrome.webdriver.WebDriver (session="4ff5299708e6e6a5b6b4c0a185e2941a")>
ibeam  | 2025-11-02 14:15:10,927|I| Logging in succeeded
ibeam  | 2025-11-02 14:15:11,012|E| Repeatedly reauthenticating failed 3 times. Killing the Gateway and restarting the authentication process.
ibeam  | 2025-11-02 14:15:11,012|I| NO SESSION Status(running=True, session=False, connected=False, authenticated=False, competing=False, collision=False, session_id=None, server_name=None, server_version=None, expires=None)
ibeam  | 2025-11-02 14:15:12,020|I| Starting maintenance with interval 60 seconds
ibeam  | 2025-11-02 14:16:12,027|I| Maintenance
ibeam  | 2025-11-02 14:16:12,028|I| Gateway not found, starting new one...
ibeam  | 2025-11-02 14:16:12,028|I| Note that the Gateway log below may display "Open https://localhost:[PORT] to login" - ignore this command.
ibeam  | 2025-11-02 14:16:12,028|I| Starting Gateway as Linux process with params: ['bash', 'bin/run.sh', 'root/conf.yaml']

[Voyz]

@jefag this seems to be an problem unrelated to this thread - could you open a new issue and let's discuss it there?

[michaeljherrmann]

To add some context on @michaeljherrmann's answer and solution:

While it's really awesome you managed to do this without any kind of browser and emulation - I'm genuinely impressed you figured out how to do it - I recall several such attempts in the past, and usually the conversation stopped when discussing whether doing so would be against IBKR terms of service with some voices raised that such direct interaction with the API could get one into trouble.

I just suggest to be wary of the TOCs to avoid having any issues with access to your account. If it wasn't for that, I'd recommend that solution over what IBeam does - it's clearly more elegant.

Thanks @Voyz and yes definitely a valid concern. I had this thought too a few years ago when I first built it. I had reached out to their support about calling the authentication apis directly and they said it's fine. While their support is likely not a lawyer, it was enough for me to be comfortable using it and I haven't had an issue since.
At the time though, they weren't allowing OAuth for individual accounts, but it sounds like people have been able to do that now so if @xjcarter you're able to get it working with OAuth that's definitely the best (and industry standard).

[Voyz]

ohh that's awesome news @michaeljherrmann ! if that's the case then congrats on your solution, and thanks for reporting back on your exchange with their support. I'd suggest you quote that conversation in your repo (if you have a copy)