26 Oracle Argus Safety Password Management—Cryptography Tool
Oracle Argus Safety uses dynamically generated encryption keys for passwords within the system. The Cryptography Key Editor allows you to generate a dynamic key and then encrypt passwords using the said key. The generated key must be installed on each application server and must be common to allow all servers to communicate with the Oracle Argus Safety database.
The key is stored in the ArgusSecureKey.ini
file located in the .\Windows folder.
IMPORTANT: During a new environment installation, a key will need to be generated prior to creating a database.
During an upgrade, a key will need to be generated prior to upgrading or an existing key from the existing setup can be used to perform the database upgrade. Make sure that the password information specified in the database is consistent with the information provided in the ArgusSecureKey.ini
file.
Note:
ArgusSecureKey.ini
file is generated, there is no need
to run this tool again while launching the Oracle Argus Safety Crypto Tool. The tool should only be run again:
- if you are resetting passwords or keys
- if you have lost the ArgusSecureKey.ini file
- if you are setting the Argus Bridge schema password
When the key file is created, copy it to the .\Windows folder on all application servers (web, transaction, etc.).
Note:
Do not run the Cryptography Key Editor on each application server to generate passwords. It need only be run once during the initial system setup. Subsequent server installations must have the key manually copied to each .\Windows folder.
For more information, see: