SSO login failed but just for one subsidiary (company) and works fine for all other subsidiariesDescriptionSSO login works perfectly for all subsidiaries (companies) except one. When a user from affected subsidiary perform an SSO login attempt, user got redirected to external_logout_complete.do reporting SAML Validation failed. When checking ServiceNow logs, you might see something like below: 1) Assertion audience mismatch. Expected: https://instance1.service-now.com, Actual: https://instance2.service-now.com2) SAML2: Assertion audience mismatch. Expected: https://instance1.service-now.com, Actual: https://instance2.service-now.com: no thrown errorYou have also verified the following: SSO configurations in ServiceNow and Audience URI is GOOD and works for all other subsidiaries. IdP admin also confirms their configurations are OK.SAML Request is generated successfully from instance1 but the received SAML Response (generated by IdP) is pointing to instance2.Release or EnvironmentAllCauseThis could be an issue with the DNS cache in customer's infrastructure.ResolutionPlease ask customer to perform DNS cache clean on their infrastructure side or to check and verify the IP address entries stored on their DNS server for the respective ServiceNow instance and that should fix the issue.