Extension Authentication Configuration
Last updated
Was this helpful?
Last updated
Was this helpful?
By default, on installation, the PixieBrix browser extension prompts the team member to link the extension to a PixieBrix account. However, if the team member closes the extension, PixieBrix will not prompt them to link the extension again.
To require a team member to log in to the PixieBrix extension, supports using to associate the extension with your organization. As part of the PixieBrix heartbeat every 5min., PixieBrix will check if it’s unlinked and prompt the user to link their extension.
In Chrome's chrome://policy/ screen, if you have the PixieBrix browser extension installed, you’ll see the policy value you've provided under the PixieBrix section. For example:
Windows Registry Setting
On Window, use the registry or ADMX policy to set the managedOrganizationId policy for the extension:
The extension policy is in the following hive:
The policies should be configured as follows:
managedOrganizationId
REG_SZ
Your team's tenant UUID
PixieBrix supports blocking access to URLs for unauthenticated users. If an unauthenticated user visits a blocked page, they will be redirected to the PixieBrix login page (or an SSO login page if SSO is enabled for your team).
Configuring the Extension Policy
managedOrganizationId
REG_SZ
Your team's tenant UUID
enforceAuthentication
REG_DWORD
1
Configuring the URL Denylist
Do not add any login flow URLs to the denylist. Adding login URLs will prevent users from authenticating.
The denylist of URLs is configured in the Admin Console, under your team's Settings page.
See the instructions at: Setting Up SAML/SSO
The PixieBrix browser extension does run not in Incognito mode.
To prevent users from bypassing the extension by using Incognito mode, set the browser extension policy to disable Incognito mode:
Provide a list of to deny.