Requirement
You would like to configure the browser extension at a central location for all users, including server mode, database profiles and a few other settings.
Prerequisites
Password Secure Server & Browser extension min. version 9.1
Extension IDs - You will need the ID of the extension in all configurations. When the extension is installed via the stores (Chrome Web Store, Edge/Add-ons, Firefox Add-ons), you can find the ID in the following table. If it was installed in any other way, the ID may differ - in this case, you can find it on your browsers' add-on management page (e.g. chrome://extensions
).
Browser | Extension ID | |
1 | Google Chrome |
bpjfchmapbmjeklgmlkabfepflgfckip
|
2 | Microsoft Edge |
ahdfobpkkckhdhbmnpjehdkepaddfhek
|
3 | Mozilla Firefox |
{3bdedc7b-4521-44e0-bffe-519f60814d95}
|
Required properties for profiles - The following list contains all profile properties that can be deployed automatically.
Value name | Mandatory? | Value data | |
1 | ID | Yes |
Unique(!) ID of the profile. Use a GUID (generate with for example guidgenerator.com).
When using the same GUID for multiple profiles, the last one will overwrite all previous!
|
2 | database | Yes |
Name of the database the connection should be established for.
|
3 | color | No |
Color of the profile in Hex format (e.g. #0068da). Used in the list of passwords, see the screenshot below.
|
4 | name | Yes |
Name of the profile that is displayed at the databases' menu when multiple profiles are existing. If only one profile exists, the name is not displayed.
|
5 | webAppAddress | Yes |
Address of your web app. Will be used when opening a password via the browser extension.
Example:
https://example.com/
|
6 | endpoint | Yes |
Endpoint for the whole communication with the server.
Example:
https://example.com/api
|
Procedure
Google Chrome
Windows
- Open the registry and go to the key
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\<extension-id>\policy
- if this path is not existing, create it- Replace
<extension-id>
with the ID of your extension
- Replace
- Create a key called
managedSettings
, containing a keyprofiles
- Inside this created key, you have to create sub-keys (counting upwards - first profile is key "1", second profile is key "2", and so on …).
- Define each property from the properties table above as REG_SZ and configure the correct value
For example, you can use the following
.reg
file to create two example profiles. Just save it to your computer and double-click it. Don't forget to change the extension ID if yours is something different.Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bpjfchmapbmjeklgmlkabfepflgfckip]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bpjfchmapbmjeklgmlkabfepflgfckip\policy]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bpjfchmapbmjeklgmlkabfepflgfckip\policy\managedSettings]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bpjfchmapbmjeklgmlkabfepflgfckip\policy\managedSettings\profiles]
; From here, profiles are starting
[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"
; Define other settings
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bpjfchmapbmjeklgmlkabfepflgfckip\policy\managedSettings\options]
"allowCrossClientAuth"=dword:00000001
Microsoft Edge
Windows
- Open the registry and go to the key
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\<extension-id>\policy
- if this path is not existing, create it- Replace
<extension-id>
with the ID of your extension
- Replace
- Create a key called
managedSettings
, containing a keyprofiles
- Inside this created key, you have to create sub-keys (counting upwards - first profile is key "1", second profile is key "2", and so on …).
- Define each property from the properties table above as REG_SZ and configure the correct value
For example, you can use the following
.reg
file to create two example profiles. Just save it to your computer and double-click it.Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ahdfobpkkckhdhbmnpjehdkepaddfhek]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ahdfobpkkckhdhbmnpjehdkepaddfhek\policy]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ahdfobpkkckhdhbmnpjehdkepaddfhek\policy\managedSettings]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ahdfobpkkckhdhbmnpjehdkepaddfhek\policy\managedSettings\profiles]
; From here, profiles are starting
[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"
; Define other settings
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ahdfobpkkckhdhbmnpjehdkepaddfhek\policy\managedSettings\options]
"allowCrossClientAuth"=dword:00000001
Mozilla Firefox
Windows
- Create a file
passwordsecure.json
at an accessible location (e.g. atC:\BrowserExtensionConfig\
) - Put the following content to the created file (don't forget to exchange the extension ID if yours is something different)
-
{ "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 at
HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\ManagedStorage\<extension-id>
- if the path is not existing, create it- Replace
<extension-id>
with the ID of your extension
- Replace
- Give the keys
(Default)
property the path to the created file as value
Comments