User Registration Methods
Once the browser extension is registered with the organization, the extension attempts to identify which user within the organization the browser belongs to. This is done to avoid the user having to interact with the extension but still providing high confidence identification. To do this the extension does the following.
The organization can deploy a policy that is specific for each machine allowing the extension to pull the user identification from the policy.
The extension queries the browser to see if a user has authenticated with the browser in the active profile (signed into the company Google or Microsoft email org).
The extension monitors logins and if a login to Microsoft or Google is observed the username of that session is used for registration.
The extension monitors logins to other websites and once 3 successful logins have been performed across 3 websites with the same username that user is used for registration.
The extension monitors use of Google or Microsoft web-based email. When user opens their email in the browser the extension uses the email of the authenticated user to register.
Once a user is identified they are submitted to the backend for verification. If the user exists in the organization and the deployment key is valid then an API key is issued to that browser profile.