This window is invoked from the Data Display window (Tools > Generate Encrypted Password).
This feature was introduced in conjunction with Batch Mode operation of AQT, in which you need to specify Connect statements in your batch scripts to sign onto the database you wish to run your script against. If your database requires a user-id and password to be specified, these will need to be coded in the script. This is a security risk - in our opinion, passwords should never be coded in clear text in scripts.
Our solution to this is to use encrypted passwords in your batch scripts. The procedure is to:
Note that there is a randomizer built into the encrypted password. The same password can produce different encrypted passwords if run more than once (this is to prevent the cracking of password by trial and error).
Three identity options are available:
You may wish to adopt a higher level of security by selecting one of the other options. With these, AQT will encrypt the password with a system-generated key that is held in your registry.
Note: for the option Anyone using this Machine to work, you must have authority to update the LOCAL_MACHINE part of your registry. Some organization networks restrict access to this.
If your machine is rebuilt, or the AQT registry entries are tampered with, the encrypted passwords will no longer work and will need to be regenerated.