Proxy can hang due to invalid OIDC connector #2690
Labels
Milestone
Comments
klizhentas
added a commit
that referenced
this issue
Jul 3, 2019
Invalid or inaccessible OIDC connectors were preventing all other logins to work, as they were grabbing mutex and making a network call. Besides, the error was not informative as the user saw "web headers timeout" error in the browser. This fix makes sure that: * Connector errors are isolated to the connector name and other flows are not blocked * Error is presented to user in a reasonable way and provides instructions * Administrator can see the error in the audit logs.
This was referenced May 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If an OIDC connector is created with an invalid
issuer_url, the Web UI and proxy locks up for a few minutes and eventually returns.During this time, all other connections hang a well. Afterwards the Web UI (and possibly proxy) remains sluggish.
The proxy needs to be restarted to resolve this problem.
The text was updated successfully, but these errors were encountered: