Repository navigation
|
I'm integrating Keycloak as a service provider with an identity provider, using SAML. When the user is authenticated, (and the trace logs enabled) I see the SAML Response decoded perfectly in the logs, but then I receive this message: 2025-03-14 13:15:03,514 TRACE [org.keycloak.saml.common] (executor-thread-9) Set Attribute Namespace=http://www.w3.org/2000/xmlns/::Qual=:xmlns:ds::Value=http://www.w3.org/2000/09/xmldsig# 2025-03-14 13:15:03,532 ERROR [org.keycloak.services.error.KeycloakErrorHandler] (executor-thread-9) Uncaught server error: org.keycloak.broker.provider.IdentityBrokerException: Could not process response from SAML identity provider. I'm suspecting that the error might be in other field rather than the SAML Response, as it is perfectly decoded in the logs (it is not shown here), but maybe in the relay state, or another field (the IdP is sending some other fields that are not used by the standard SAML protocol, and maybe it causes keycloak to break?) Thank you so much for your help :) |
Replies: 1 comment 1 reply
|
Solved: it was because the RelayState was coming with an "&" and it was causing the base64.decode function to cause an exception. |
|
I also got a similar "IOException Bad Base64 input character decimal" error running keycloak but the logs thrown doesn't explicitly point out what to fix to solve the issue. How were you able to troubleshoot your issue? I posted my question with the logs that I got here. |
Solved: it was because the RelayState was coming with an "&" and it was causing the base64.decode function to cause an exception.