Login Message: Resume login

[dimer28]

I recently opened a new account for my corp, and it defaulted to the Mobile Authenticator App.
The IBC pops up the code window. After I get the code in successfully, the next window popup is:

Until I press the Resume login button, it does not enter the system. There is no timeout on that screen.

The next day after the automatic re-login kicks in, the authorisation code is not asked for anymore, but the Resume Login window does pop up. And until I click the button, it is not logged in.

Is there a way to automate the click or remove the Resume login window?

[rlktradewright]

IBC does not currently support Mobile Authenticator Apps. The question is whether it is worth enhancing it to do so.

First, let me point out that IBC does provide extensive support for 2FA via the IBKR Mobile App, so you might want to consider using that instead. It has a number of advantages:

• you don't need to be anywhere near the computer at the time that IBC initiates login, provided you have your phone with you (and switched on) and you have internet access
• if you miss the 2FA alert (which times out after 3 minutes) IBC will repeat the process so you get another chance: in fact this will continue until you eventually do handle the alert or close TWS/Gateway
• you don't have to manually type any code

If you really don't want to use IBKR Mobile App (in which case I'd appreciate you explaining your reasons), then I see no obvious reason why it shouldn't be possible to enhance IBC to deal with the windows you mentioned. (Note that IBC does not pop up these windows, TWS/Gateway do that. However IBC should be able to recognise and intercept them to press the appropriate button.)

Since my Live account is in use 24X5 (I currently use IBKR Mobile for 2FA), I'd have to do the necessary investigation and development work either late at night when the markets have no interest for me or at the weekends. It should be pretty
straightforward to do, but you might need to be patient for a couple of weeks.

So let me know if you really need this.

Oh just one point: IBC won't be able to fully automate this: you'd still need to manually enter the authentication code.

[dimer28]

Thanks for your reply, Richard.

Gmail - Important Security Update_ Mand...pdf

I do use IBKR Mobile for 2FA for my personal account. But I recently got an email from IB, see attached (I removed all my personal info). The email states that users are expected to switch to another TOTP Application.

And when I went to my newly created corp account to add "IBKR Mobile for 2FA" the option is not there, only third-party TOTPs.

Perhaps IBKR is going away from its mobile authorisation for the new accounts.
Yes, I do like the "IBKR Mobile for 2FA" as there is no need to enter the code.

Regards,
Dmitri

[rlktradewright]

Oh, well that's a surprise. I'll certainly see what I can do to help with this.

It's not clear to me from the letter that all users are going to be required to use TOTPs, perhaps just Financial Advisor clients. Agreed it does say '... for all clients using ...', but the letter is only addressed to Financial Advisors, and clients using ordinary accounts have been required to use 2FA for a couple of years now. (Is it really the case that FA accounts could get away without 2FA till now?)

I really hope they don't insist on this for everyone. 2FA using IBKR Mobile is just so convenient (even though I've never had to use it while away from home).

[dimer28]

Thank you so much!!! If you'd like me to test it when the time comes, please let me know.

[rlktradewright]

I've been looking at this over the weekend, and it's all been very positive, as well as somewhat puzzling in light of what you reported.

What I found was that I didn't have to do anything to support the Mobile Authenticator, apart from enabling that option in Account Management and setting:

SecondFactorDevice=Mobile Authenticator app

in config.ini.

So now I can use either IBKR Mobile or Mobile Authenticator, and switch between them by changing the SecondFactorDevice setting.

The puzzling bit is that I haven't seen any sign of the window with the Resume Login button (with either stable version 1030 or latest version 1039). I suppose it's possible that yours might behave differently because it's a Financial Advisor account, but this seems very unlikely. Perhaps IBKR have decided they don't need this spurious extra window after all. So are you still seeing it with the latest updates?

[dimer28]

Thank you for your reply, Richard. My FA account is still working fine, as it uses IBKR Mobile

The new account where I am facing the "Resume Login" Pop-up is the Organisational account, which is an IBLLC-US based entity.

Here is the screenshot. The new account allows only Mobile Authenticator, no other options.

So, potentially, the pop-up is affecting all the newly opened corporate accounts in the US.

I had changed the setting to: SecondFactorDevice=Mobile Authenticator app in the config (before it was empty)
I also updated to the 1039 TWS
Still the same pop-up as previously after entering the mobile code.

Regards,

[rlktradewright]

Ok, well I should still be able to deal with this window. I'll need some diagnostics to make sure I can get IBC to recognize it and click the button.

To do this, set the following in config.ini (near the end of the file):

LogStructureScope=unknown
LogStructureWhen=activate

Then run IBC until the relevant window has appeared and send me the IBC logfile.

By the way, if you only have a single 2FA device registered in your account, you don't need the SecondFactorDevice setting at all.

[rlktradewright]

Sorry, that's no good - you havent set the required settings in config.ini:

LogStructureScope=unknown
LogStructureWhen=activate

so the logfile doesn't include the diagnostics I need.

[dimer28]

Here is the updated log file:

IBC-3.23.0_TWS-1039_MONDAY.txt

Thank you

[rlktradewright]

Almost right!

I've never noticed this over the past 22 years, but trailing spaces in the value of a setting in config.ini are not stripped off, and you have one after "unknown", which is therefore being parsed as "unknown ", and therefore not recognised, and therefore defaults to "known", and therefore the "Login Messages" dialog is ignored.

So please remove that space and try again.

I'll fix that bug in the next version.

[dimer28]

Thank you, Richard.
Here is LogStructureScope set to 'unknown'

IBC-3.23.0_TWS-1039_MONDAY.txt

Have a great day!
Dmitri

[rlktradewright]

I've produced a new version that I hope will do the trick. This window appears to actually have two buttons, and it's not clear which I need to click, so I've chosen one and it will probably be the wrong one! If so, I'll build it again to use the other one.

The updaated zip file is here:

https://1drv.ms/u/c/599f0c96432c9f5a/EbDkT5CmYAVPnMQ3pmOpVuYB91c-zc3JhBECpzb3h0DgCw?e=wBf43X

All you need to do is extract the IBC.jar and version files and overwrite your existing ones.

[dimer28]

The message is still there. By the way, it could take 4-6 seconds to load the pop-up window.

[rlktradewright]

Logfile please

[rlktradewright]

Did you see my request for the logfile? I need to see that before I decide what to do next. I realise it didn't work as hoped, but I still need to see what information was logged, to make sure I haven't done something stupid.