The Browser Policy Single Sign On (SSO) allows the Browser Extension to identify the user without having to go through SSO via SAML altogether.
To smoothly roll out Userlane, ensure the Browser is configured to install the Userlane Extension using the options provided by the respective browser.
This article focusses on its implementation on Chrome.
Installation on Google Chrome
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist] "1"="oaienfpdbimabhlgjlbdpocbogaijnam" |
Note: The Registry Key ("1") might need to be modified (counted up to the ones already existing) if multiple Browser Extensions (other than Userlane) are installed.
Configuring
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\oaienfpdbimabhlgjlbdpocbogaijnam\policy];same values as for Edge (see Chapter Configuring in Edge)
Validating Browser Policies |
In Chrome, you can use the following links:
chrome://policy - to confirm that the ExtensionInstallForcelist value is present.
- chrome-extension://oaienfpdbimabhlgjlbdpocbogaijnam/options/index.html?stay#/nativeconfig - to confirm that the companyId, companyIntegrity, authToken, region, and/or userId values are present.
