SAML2ValidationError : SSO not working -User is logged outIssue When attempting to log in via SSO, users are being redirected to the logout page. Upon investigating the live SAML logs by replicating the issue, the following errors are observed: 1)SAML2: Failed to validate signature profile. Signature cryptographic validation not successful2)SAML2ValidationError: Signature cryptographic validation not successfulReleaseALLCauseThe instance is sending the SAML request using a specific certificate that is mapped to the IDP within the instance. However, the IDP is not providing the intended response by utilizing the same certificate.For example : request is sent using the xxxx certificate ,but the response is provided by the IDP using the yyyy certificate, resulting in a failure to allow users to authorize successfully.Enable the "glide.authenticate.multisso.debug" property by setting it to true while reproducing the issue.Upon reviewing the backend logs, the error encountered during authorization is "SAML2ValidationError: Signature cryptographic validation not successful." This occurs during the SAML login flow when the SAML response message is validated to ensure the SAML assertion is correctly signed by the correct Identity Provider (IdP) and is using the given trust store certificate.When the certificate is incorrect, it throws a "Failed to validate signature profile" error, along with "Signature cryptographic validation not successful."ResolutionTo resolve this issue, I recommend reaching out to your IDP team to create a new certificate. Once obtained, add the new certificate to the instance and associate it with the current IDP record.To create a new certificate after obtaining it from your IDP team, please follow this knowledge base article (KB):KB:https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0691439