XMLSecurity exception while decrypting: Errors occurred during de-serialisation
Rod Widdowson
rdw at steadingsoftware.com
Thu Feb 19 11:22:46 UTC 2026
> ERROR Shibboleth.SSO.SAML2 [17] [default]: failed to decrypt assertion: XMLSecurity exception while decrypting: Errors occurred
during de-serialisation of decrypted element content
AFAICS this originally bubbles up from Xerces when it looks at the XML you gave it, which might (and I am no expert) argue
corruption by the browser or "on the wire". I'm not sure what logging support Xerces-C has...
> Any ideas? At least what to focus on, debug logging on the SPs or on
> the IDP or both?
Not really. Just some questions
- Is it always the same person? Or can it work for someone one day and fail the next?
- If it's the same person, what is the browser? This seems unlikely
- You might want to try to get hold of the assertion at the IdP (org.opensaml.saml.saml2.encryption.Encrypter to DEBUG) and
check that it is OK (It will be)
- I guess there is a way to log the incoming message at the SP as well, less sure about that.
But I'm grasping at straws until the US wakes up....
/Rod
More information about the users
mailing list