-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Medium
-
Component/s: Identity Internal - G Suite, Identity Internal - SAML
-
None
Summary
Having a G Suite integration for the same domain being used in a SAML integration can cause inconsistencies over the managed users data.
Steps to Reproduce
- Create a user in G Suite with the email user@test.com and last name userGSuite
- Integrate G Suite in the instance for the domain test.com(this should generate a user in user management for the G Suite user)
- In your IdP create a user with the same email(user@test.com) and last name userIdP
- Create an organization do the SAML setup with your IdP
Now when the user logs in the instance with SSO his user full name will be updated to userIdP and when a sync from G Suite runs it will be updated back to userGSuite
E.G using André Kasper(Gsuite) and André Kasper(Azure):
Again, this will be set back to André Kasper(Gsuite) on the next google sync and to André Kasper(Azure) on every login.
Notes
Also, when having an organization using the domain and then verifying it in google and integrating with GSuit the SAML domain will be flagged as SUPERSEDED and the SAML integration will stop working until you verify the domain again.