401 http status for un authorized request in apli_tickle container #6
Answered
by
Jonjinadsf
Jonjinadsf
asked this question in
Q&A
-
Beta Was this translation helpful? Give feedback.
Answered by
Jonjinadsf
Jul 18, 2025
Replies: 2 comments
-
|
Problem solved. IBKR now is use two stage authorization for security which means logging in the gateway will only give you the SSO authorization. But user still needs to get brokerage session authorization through Isever again.
After reauthorization problem solved.
Working on add this into the dockerfile so this process will be autonomous. where do you think should be better to add it @rcontesti ?
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
Jonjinadsf
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment







Here is the final solution I added reauthorization in the health check of the tickle container and now it is working. (PS: I am not sure will there be a interval to reauthorize, and we will figure in the future.