When you need to include sensitive passwords in your config files and want to ensure that they're encrypted so they can't be easily seen be users looking at the configuration files.
Add the steps involved:
encrypt
command to encrypt a clear text passwordGo to to the osgi console and type encrypt <
and press return e.g.password>
osgi> encrypt My$upaSekrutP@sswurd ENCKPXBCTMGGMKBGKPK |
Copy the encrypted password from the console and paste it back into the configuration file replacing the original password
<username>bob</username> <password>My$upaSekrutP@sswurd<password> |
<username>bob</username> <password>ENCKPXBCTMGGMKBGKPK<password> |
The encryption key used to encrypt the passwords is stored in the file called This file is generated the first time Weave starts and will be unique for each Weave instance, which means that encrypting the same password with different instances of Weave would result in different encrypted text. This means that if you want to re-use the same configuration files on multiple Weave instances, for example development and production, then you need to either:
Additionally, for extra security the permissions on that file should be set to only allow the users running the Weave instance to read the |
Also refer to the following sections of the Weave System Administrator Guides: |
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|