Obfuscating server passwords

You can replace the passwords on the server with obfuscated passwords, by indicating the type of password that you want to replace and the new password.

The password is obfuscated and stored in the registry on Windows systems and in the configuration files on Linux systems.

Run the following command to obfuscate server password:
On Windows systems:
BESAdmin.exe /updatepassword /type:<type> [ /password:<password> ]
/sitePvkFile:<path+license.pvk> [ /sitePassword:<pvk_password> ]
where:
type:<type>
Specifies one of the following types of password:
server_db
The password to be updated and recorded obfuscated is related to the connection with the server database
dsa_db
The password to be updated and recorded as obfuscated is related to the connection with the DSA database
password:<password>
Specifies the password to be obfuscated and then recorded.
sitePvkFile:<path+license.pvk>
Specifies the private key file (filename.pvk). This private key file and its password are required to run the Administration Tool. Only users with access to the site level signing key and password are able to create new BigFix operators.
Note: The notation <path+license.pvk> used in the command syntax stands for path_to_license_file\license.pvk.
sitePassword:<password>
Specifies the password associated to the private key file (filename.pvk). This setting is optional, if you omit it you will be asked to specify the password interactively when the command runs.
On Linux systems:
where:
type=<type>
Specifies one of the following types of password:
server_db
The password to be updated and recorded obfuscated is related to the connection with the server database
dsa_db
The password to be updated and recorded as obfuscated is related to the connection with the DSA database
password=<password>
Specifies the password to be obfuscated and then recorded.
sitePvkLocation=<path+license.pvk>
Specifies the private key file (filename.pvk). This private key file and its password are required to run the Administration Tool. Only users with access to the site level signing key and password are able to create new BigFix operators.
Note: The notation <path+license.pvk> used in the command syntax stands for path_to_license_file/license.pvk.
-sitePvkPassword=<password>
Specifies the password associated to the private key file (filename.pvk). This setting is optional, if you omit it you will be asked to specify the password interactively when the command runs.