Multiple x509 certificates result in the error 'SAML2: Failed to validate signature profile.:No thrown error'Issue When there are multiple x509 certificates available on the instance, that can sometimes result in the following error being thrown 'SAML2: Failed to validate signature profile.:No thrown error'ReleaseOrlando/Paris release and above.CauseIf even after replacing the IdP certificates the users are not facing any issues and are successfully able to login to the instance. These type of errors usually come up when you have multiple SSO certificates defined in the IdP Record under "X.509 Certificates".ResolutionWhen there are multiple x509 certificates available in the instance, all of them are matched with the certificate information sent in the SAML Response from the Identity Provider when a user tries to login to the instance using SSO authentication. While going through the system logs we can observe that the error 'SAML2: Failed to validate signature profile.' shows up multiple times when a user tries to login since the other certificates will not match with the response. As long as one of the certificates matches to what is coming in the SAML Response from the IdP (Identity provider) then there should be no real issue in that case and the error can be ignored. Hence, we can say that in most cases the error 'SAML2: Failed to validate signature profile.' doesn't always signify a problem in the instance/IdP setup.Related LinksAlso attaching screenshots for reference.