You have configured SSO using a third-party IDP with your Google Workspace domain. An end user has reported that they cannot sign in to Google Workspace after their username was changed in the third-party SSO product. They can sign in to their other internal applications that use SSO, and no other users are experiencing issues signing in. What could be causing the sign-in issue?
The SAML assertion provided by the third-party IDP is presenting a username that conflicts with the current username configured in Google Workspace. Since the user can sign in to other internal applications but not Google Workspace, it indicates an issue specific to the Google Workspace configuration. Changing the username in the third-party SSO product means the SAML assertion likely contains the new username, which does not yet match the username configured in Google Workspace, causing the sign-in issue.
A is correct.
Would go A
Answer is A Username was changed.
A. The SAML assertion provided by the third-party IDP is presenting a username that conflicts with the current username configured in Google Workspace.
Agree with A