You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As recently as Dec 12, I was able to run ibeam and authenticate by responding to the IBKey popup. At some point in the past week, however, this stopped working, and now the IBKey popup flow breaks; this only occurs for login attempts happening through ibeam (or its proxy server), not when I log in to the same account directly by web (for which the IBKey popup flow works just fine). I've reproduced the behavior on two IB logins and three machines with distinct IP addresses.
open the notification -> select "approve" -> authenticate
login flow continues in ibeam
Observed behavior
IBKey notification appears
open the notification -> select "approve"
IBKey shows the following:
ibind never receives a 2FA/IBKey auth
Reproduced across two logins, three machines with distinct IP addresses, and multiple days. Same behavior whether the login attempt is from ibeam_starter itself or navigating to https://localhost:5000/sso/Login?RL=1&locale=en_US once ibeam is running on port 5000.
Environment
IBeam version: 0.5.6
Docker image or standalone: docker image
Python version (standalone users only): []
OS: Ubuntu 22.04 (reproduced on 24.04)
Additional context
This might be a red herring, but it's my current best guess. Navigating to https://localhost:5000/sso/Login?RL=1&locale=en_US using Chrome reveals that a POST to /portal.proxy/v1/gsss/bulletins is getting 404. This 404 does not occur when hitting https://ndcdyn.interactivebrokers.com/sso/Login?RL=1&locale=en_US directly in Chrome incognito. Logs from a proxy that I introduced for better logging:
inputs/san.cnf taken from template. I am using self-signed cacert.jks / cacert.pem certificates produce according to instructions; these same certs had previously worked fine for ibeam login.
I spent a supremely unproductive 32 minutes on the phone with IB's Technical Assistance team; when I confirmed that I was able to log in correctly from other machines than the affected one, the rep suggested that I "talk with my company's IT team", "talk with my company's networking team", and that they "do not troubleshoot device-specific issues" (which this was as I was able to login from other devices).
Suggest a Fix
Honestly, I'm baffled.
The text was updated successfully, but these errors were encountered:
hey @rossry thanks for describing your issue in so much detail and I'm sorry you're struggling with it.
To be honest, I'm baffled as well. If it works on some machines but not on the others than it could be some network configuration related to that bad machine. But as for specifics, I wouldn't know what else to suggest. Maybe try a different cloud provider? Can you see anything else that could be done here?
Describe the bug
As recently as Dec 12, I was able to run ibeam and authenticate by responding to the IBKey popup. At some point in the past week, however, this stopped working, and now the IBKey popup flow breaks; this only occurs for login attempts happening through ibeam (or its proxy server), not when I log in to the same account directly by web (for which the IBKey popup flow works just fine). I've reproduced the behavior on two IB logins and three machines with distinct IP addresses.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Observed behavior
Reproduced across two logins, three machines with distinct IP addresses, and multiple days. Same behavior whether the login attempt is from
ibeam_starter
itself or navigating tohttps://localhost:5000/sso/Login?RL=1&locale=en_US
once ibeam is running on port 5000.Environment
IBeam version: 0.5.6
Docker image or standalone: docker image
Python version (standalone users only): []
OS: Ubuntu 22.04 (reproduced on 24.04)
Additional context
This might be a red herring, but it's my current best guess. Navigating to
https://localhost:5000/sso/Login?RL=1&locale=en_US
using Chrome reveals that aPOST
to/portal.proxy/v1/gsss/bulletins
is getting 404. This 404 does not occur when hittinghttps://ndcdyn.interactivebrokers.com/sso/Login?RL=1&locale=en_US
directly in Chrome incognito. Logs from a proxy that I introduced for better logging:This request is created in the following clientside javascript on
/sso/Login
:inputs/conf.yaml
:inputs/san.cnf
taken from template. I am using self-signedcacert.jks
/cacert.pem
certificates produce according to instructions; these same certs had previously worked fine for ibeam login.env.list
:I spent a supremely unproductive 32 minutes on the phone with IB's Technical Assistance team; when I confirmed that I was able to log in correctly from other machines than the affected one, the rep suggested that I "talk with my company's IT team", "talk with my company's networking team", and that they "do not troubleshoot device-specific issues" (which this was as I was able to login from other devices).
Suggest a Fix
Honestly, I'm baffled.
The text was updated successfully, but these errors were encountered: