Hello All,
We have recently upgraded the OTDS to version 24.3. After that, we are unable to log into OTCS using SSO. Once we hit the OTCS URL, it is going to the IdP Metadata URL configured under the Auth handler in OTDS. After that it is again showing the OTDS sign on the screen. In the log we are getting the following errors. Although we have not changed anything on the SSO or auth handler side during the upgrade process. Any help tofix this would be appreciated.
javax.xml.crypto.dsig.XMLSignatureException: cannot find validation key
|DEBUG |[https-jsse-nio-443-exec-6]|SAML2Handler||NameID in SAML Assertion is SARKARR
|DEBUG |[https-jsse-nio-443-exec-6]|ReplayCache||uuid added to replay cache: SAML_https://sts.windows.net/505cca53-5750-4134-9501-8d52d5df3cd1/__4c6dbedd-a06a-477d-a6d7-22cf22eca000
|DEBUG |[https-jsse-nio-443-exec-6]|OtdsAuthenticationManager||Authentication attempt with handler devAzureSAML result {SUCCESS, null, null, SARKARR}
|ERROR |[https-jsse-nio-443-exec-6]|OtdsAuthenticationManager||Error during authentication handler processing:
java.lang.IllegalArgumentException: Invalid DN format
