(I don't understand why AgID is not returning the expected human message leaving the interpretation to the SP, but anyway...)
@lscorcia do you know if there's any way to map SAML statuses in Keycloak or if we need to approach this with extension?
After some digging, I think it's enough to localize the message in SpidSAMLEndpoint. handleLoginResponse but no real clue on how to handle the fact that AgiID is returning a semi-human message ErrorCode nr19 in place of a proper error code (that would be easily localized through standard).
AGID requirement
As per SPID – Tabella messaggi di anomalia V1.3
in case of
it's expected to
SAML reference
Shortly, we should map the returned
<samlp:StatusMessage>
(SAML11StatusType.statusMessage
in Keycloak) to something "human"otherwise the raw message is shown in Keycloak
(I don't understand why AgID is not returning the expected human message leaving the interpretation to the SP, but anyway...)
@lscorcia do you know if there's any way to map SAML statuses in Keycloak or if we need to approach this with extension? After some digging, I think it's enough to localize the message in SpidSAMLEndpoint. handleLoginResponse but no real clue on how to handle the fact that AgiID is returning a semi-human message
ErrorCode nr19
in place of a proper error code (that would be easily localized through standard).SPID-SAML-check example