Goal
You configure the Browser Extension centrally for all users, including server mode, database profiles, and other settings. You distribute the configuration through policies in the Windows registry (Chrome and Edge) or through a configuration file (Firefox).
Prerequisites
- Password Secure Server and Browser Extension version 9.1 or later.
- The ID of the extension. It is required in all configurations. If you installed it from the stores, these IDs apply:
If you installed it another way, the ID can differ. You can then find it on the extension management page of your browser, for exampleBrowser Extension ID Google Chrome bpjfchmapbmjeklgmlkabfepflgfckipMicrosoft Edge ahdfobpkkckhdhbmnpjehdkepaddfhekMozilla Firefox {3bdedc7b-4521-44e0-bffe-519f60814d95}chrome://extensions.
Steps
Define profiles
Each profile consists of the following properties. You use these properties in all three browsers.
| Property | Required | Description |
|---|---|---|
id |
Yes | Unique ID of the profile. Use a GUID, for example generated with guidgenerator.com. If you use the same GUID for several profiles, the last profile overwrites all previous ones. |
database |
Yes | Name of the database to connect to. |
color |
No | Color of the profile in hex format, for example #0068da. It is used in the password list. |
name |
Yes | Name of the profile. It appears in the database menu when several profiles exist. With only one profile, the name is not shown. |
webAppAddress |
Yes | Address of your Web App. It is used when a password is opened from the Browser Extension. Example: https://example.com/
|
endpoint |
Yes | Endpoint for all communication with the server. Example: https://example.com/api
|
Google Chrome (Windows)
- Open the registry and navigate to the key
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\<extension-id>\policy. Create any missing keys. Replace<extension-id>with the ID of your extension. - Create the key
managedSettingswith the subkeyprofiles. - Under
profiles, create one subkey per profile, numbered in ascending order (1,2, and so on). - In each profile key, create all properties from the table as
REG_SZand enter the values.
Alternatively, save the following .reg file with two example profiles, adjust it, and run it with a double-click. Change the extension ID if yours differs. The value allowCrossClientAuth enables cross-client authentication.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bpjfchmapbmjeklgmlkabfepflgfckip\policy\managedSettings\profiles\1]
"id"="c62d0f1b-85e1-4661-b2f2-cdf84de471ca"
"color"="#ff85ff"
"name"="Profile #1"
"webAppAddress"="https://example1.com/"
"endpoint"="https://example1.com/api"
"database"="Profile1_DbName"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bpjfchmapbmjeklgmlkabfepflgfckip\policy\managedSettings\profiles\2]
"id"="6e68336a-ea85-4a86-8a84-346e84e0bc1a"
"color"="#1b549b"
"name"="Profile #2"
"webAppAddress"="https://example2.com/"
"endpoint"="https://example2.com/api"
"database"="Profile2_DbName"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bpjfchmapbmjeklgmlkabfepflgfckip\policy\managedSettings\options]
"allowCrossClientAuth"=dword:00000001
Microsoft Edge (Windows)
- Open the registry and navigate to the key
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\<extension-id>\policy. Create any missing keys. Replace<extension-id>with the ID of your extension. - Create the key
managedSettingswith the subkeyprofiles. - Under
profiles, create one subkey per profile, numbered in ascending order (1,2, and so on). - In each profile key, create all properties from the table as
REG_SZand enter the values.
Alternatively, save the following .reg file with two example profiles, adjust it, and run it with a double-click.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ahdfobpkkckhdhbmnpjehdkepaddfhek\policy\managedSettings\profiles\1]
"id"="c62d0f1b-85e1-4661-b2f2-cdf84de471ca"
"color"="#ff85ff"
"name"="Profile #1"
"webAppAddress"="https://example1.com/"
"endpoint"="https://example1.com/api"
"database"="Profile1_DbName"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ahdfobpkkckhdhbmnpjehdkepaddfhek\policy\managedSettings\profiles\2]
"id"="6e68336a-ea85-4a86-8a84-346e84e0bc1a"
"color"="#1b549b"
"name"="Profile #2"
"webAppAddress"="https://example2.com/"
"endpoint"="https://example2.com/api"
"database"="Profile2_DbName"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ahdfobpkkckhdhbmnpjehdkepaddfhek\policy\managedSettings\options]
"allowCrossClientAuth"=dword:00000001
Mozilla Firefox (Windows)
- Create the file
passwordsecure.jsonin an accessible location, for exampleC:\BrowserExtensionConfig\. - Paste in the following content. Change the extension ID in
nameif yours differs.{ "name": "{3bdedc7b-4521-44e0-bffe-519f60814d95}", "description": "Configuration file for the Netwrix Password Secure Firefox browser extension", "type": "storage", "data": { "managedSettings": { "profiles": [ { "id": "c62d0f1b-85e1-4661-b2f2-cdf84de471ca", "color": "#ff85ff", "name": "Profile #1", "webAppAddress": "https://example1.com/", "endpoint": "https://example1.com/api", "database": "Profile1_DbName" }, { "id": "6e68336a-ea85-4a86-8a84-346e84e0bc1a", "color": "#1b549b", "name": "Profile #2", "webAppAddress": "https://example2.com/", "endpoint": "https://example2.com/api", "database": "Profile2_DbName" } ], "options": { "allowCrossClientAuth": true } } } } - Open the registry and navigate to the key
HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\ManagedStorage\<extension-id>. Create any missing keys. Replace<extension-id>with the ID of your extension. - Set the value of
(Default)to the path of the file you created.