User Tools

Site Tools


specifying_encryption_key_for_encrypting_configuration_fields

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
specifying_encryption_key_for_encrypting_configuration_fields [2016/03/09 10:42]
dloo
specifying_encryption_key_for_encrypting_configuration_fields [2016/03/09 10:43] (current)
dloo
Line 8: Line 8:
   - install the agent and change directory to the agent'​s base directory (or locate the previously installed agent'​s base directory).   - install the agent and change directory to the agent'​s base directory (or locate the previously installed agent'​s base directory).
   - change directory into the //conf// configuration folder where the **agent.xml** file is located.   - change directory into the //conf// configuration folder where the **agent.xml** file is located.
-  - create a file named **sesame.txt** and save your secret key (ascii text) in this file.+  - create a file named **sesame.txt** and save your secret key (ascii text, 1 line, no carriage return) in this file.
   - edit **agent.xml** and locate fields that are prefixed with "​encrypted:",​ these are the fields that have previously been encrypted, you will now replace them with "​encrypt:<​password>"​ where <​password>​ is the password you were previously given during agent provisioning,​ or is your selected passphrase for encrypting data from your data sources.   - edit **agent.xml** and locate fields that are prefixed with "​encrypted:",​ these are the fields that have previously been encrypted, you will now replace them with "​encrypt:<​password>"​ where <​password>​ is the password you were previously given during agent provisioning,​ or is your selected passphrase for encrypting data from your data sources.
   - restart the agent.   - restart the agent.
  
 Edit or view the **agent.xml** file again and you should see that the previously prefixed "​encrypt:"​ fields are now updated with the "​encrypted:"​ prefix and the preceding values encrypted with your private key that is stored in the **sesame.txt** file. Edit or view the **agent.xml** file again and you should see that the previously prefixed "​encrypt:"​ fields are now updated with the "​encrypted:"​ prefix and the preceding values encrypted with your private key that is stored in the **sesame.txt** file.
specifying_encryption_key_for_encrypting_configuration_fields.txt ยท Last modified: 2016/03/09 10:43 by dloo