Connected but not authenticated

[sidfeiner]

Describe the bug
Hey :)
I've been trying to use ibeam and I've successfully connected after 2fa but none of the APIs actually work. When I check my authentication status I see that it is because authenticated is set to false, although connected is set to true.
I've tried using the authentication / session inits from the docs but none of them worked.
Although, when I downloaded the latest gateway client, all I had to do was connect normally (once through the browser + 2fa) and then I was immediately authenticated and able to run all API calls.

To Reproduce
Steps to reproduce the behavior:

1. run docker run --env-file ibeam.env -p 5000:5000 voyz/ibeam when ibeam.env contains your authentication variables (IBEAM_ACCOUNT, IBEAM_PASSWORD)
2. After connection, send POST to https://localhost:5000/v1/api/iserver/auth/status
3. check authenticated field

Expected behavior
To have authenticated: true

Environment
IBeam version: 0.3.0
Docker image or standalone: Docker image
Python version (standalone users only):
OS:

Additional context
Add any other context about the problem here.

Suggest a Fix
I don't know what the problem exactly is, I've tried re-building the image with the latest gateway client but I haven't had any success because when it tries accessing the login page it shows access denied. If nobody here has some quick fix then I'll keep investigating this issue.

Thanks!

[Voyz]

Hey @sidfeiner welcome to IBeam! 😊

Thank you very much for describing your issue in so much detail - I appreciate it! At the same time, I'm sorry to say that this seems to be a duplicate of this (not so well named) other issue #19. Just like there, my suggestion would unfortunately come down to:

I'd recommend you get in touch with the IBKR support and try to work with them to figure out why the authentication fails despite providing correct credentials. I'm sorry I cannot be of more help, but this is a known problem that we cannot jump over on IBeam side despite multiple attempts. Feel free to suggest any fixes if you can think of any.

In reality this seems to be a matter of luck - not which version of the Gateway we're running. I'd recommend these steps to verify this statement.

It sucks, but it's a known problem and the solution lays on IBKR side, therefore pushing them to fix it is the only way we've found so far. As with other users running into this issue - if you can think of some intermediate solution, please feel free to share it. Thanks!

[Voyz]

Hey @sidfeiner I'm going to close this issue as a duplicate. Feel free to reopen if you feel you'd like to continue the discussion. Thanks for reporting nevertheless!