How is the Google SSO OAuth grant mapped to an app in Zluri?

How does Google Workspace identify users Logging in to different Applications using “Sign in through Google”?

Every time a user/employee logs in to an application using “Sign in through Google”, a new “token” is generated. Zluri collects these tokens and maps them to the user using the information coming in through Google Workspace’s APIs. 

Google Workspace's integration data defines which user is logging into which application. 
The integration data shares just the display text of applications rather than sharing the link for the app that is logged in. For example - “
displayText: "Microsoft apps & services".


Zluri uses that display text to map the user's login information to the applications present in Zluri’s own Database. 


This display text varies from the actual app link & names with what Zluri has in its database.


As there is currently no way to verify which app this “display text” belongs to, the mapping of users to the applications changes when the display text changes; that’s why duplication of applications is present in Zluri with similar names like “Chorus” & “Chorus.ai”, which in term are same, but Google Workspace does differentiate them as the display text is different for both of them. 


What Zluri suggests is to merge similar applications to not create any further confusion between duplicate applications. 

Can’t find what you are looking for? Let us help you!

How is the Google SSO OAuth grant mapped to an app in Zluri?

Modified on Tue, 05 Sep 2023 at 02:48 PM

How does Google Workspace identify users Logging in to different Applications using “Sign in through Google”?

Every time a user/employee logs in to an application using “Sign in through Google”, a new “token” is generated. Zluri collects these tokens and maps them to the user using the information coming in through Google Workspace’s APIs. 

Google Workspace's integration data defines which user is logging into which application. 
The integration data shares just the display text of applications rather than sharing the link for the app that is logged in. For example - “
displayText: "Microsoft apps & services".


Zluri uses that display text to map the user's login information to the applications present in Zluri’s own Database. 


This display text varies from the actual app link & names with what Zluri has in its database.


As there is currently no way to verify which app this “display text” belongs to, the mapping of users to the applications changes when the display text changes; that’s why duplication of applications is present in Zluri with similar names like “Chorus” & “Chorus.ai”, which in term are same, but Google Workspace does differentiate them as the display text is different for both of them. 


What Zluri suggests is to merge similar applications to not create any further confusion between duplicate applications. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article