Repository navigation
502 Bad Gateway error due to org.keycloak.broker.provider.IdentityBrokerException #38301
Unanswered
SatheeshSP
asked this question in
Q&A
Replies: 1 comment
|
Hi team, Any updates on the above mentioned issue. I'm requesting to please prioritize this ticket. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Before reporting an issue
Area
authentication
Describe the bug
I previously reported a similar 502 Bad Gateway error in GitHub Issue #37211, which was resolved at that time by updating the following parameter:
value: 'false'
Recently, we have started encountering the same issue again, though much less frequently than before. The errors are related to java.net.SocketTimeoutException and java.net.SocketException, along with occasional 502 errors for org.keycloak.broker.provider.IdentityBrokerException.
Could you please suggest a proper solution to address this recurring issue?
Version
latest
Regression
Expected behavior
No 502 errors should be reported for the specified API call.
Actual behavior
Getting 502 error page when API request is not completed.
GET /realms/{realm_name}/broker/{client_identity_provider_name}/endpoint
How to Reproduce?
Please help us to resolve this issue
Anything else?
No response
All reactions