To anyone who comes across this issue in the future:
In my case, the problem was resolved by deleting all existing IdP (Identity Provider) configurations and creating a new IdP configuration from scratch. After recreating the configuration, everything worked as expected.
This appears to be a unique scenario, but recreating the IdP configuration may be worth trying if you encounter a similar issue.
Thank you for taking the time to review this question. Your assistance is greatly appreciated!
Hi Jhansi,
I wouldn't recommend deleting the Encryption module, especially since your application was already working with SSO before the upgrade. Removing it won't affect existing production data, but it can break the SAML implementation and won't address the root cause.
Looking at the stack trace, the important part is:
java.lang.NullPointerException: null algorithm nameKeyPairGenerator.getInstance(...)
This usually indicates that the key/signature algorithm is coming through as empty when the SAML module tries to generate the keystore.
After upgrading from 9.6.10 → 10.24.9, I'd check the SAML configuration record and make sure the cryptographic algorithms are populated, for example:
RSA_SHA256RSA_OAEP (or the value expected by your IdP)Also try:
The null algorithm name error usually points to a missing or invalid SAML algorithm configuration rather than the Encryption module itself.
Kindly mark this as the accepted answer if it helps.