Skip Headers

Oracle Argus Safety Installation Guide Release 7.0.3 E40575-02 |
| Contents

Previous | Next |

# 14 Argus Password Management - Cryptography Tool

This chapter provides instructions for using the Cryptography tool in Argus Safety.

## Cryptography Tool Overview

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 Argus Safety Database.

The key is stored in the ArgusSecureKey.ini file located in the .\Windows folder.

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. You must also ensure that the password information specified in the database is consistent with the information provided in the ArgusSecureKey.ini file.

Once the key file has been created, it should be copied 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.

Note: Once the ArgusSecureKey.ini file has been generated, there is no need to run this tool again while launching Argus Safety Schema Creation Tool. The tool should only be run again if you are resetting passwords, keys or have lost the ArgusSecureKey.ini file.

## Installing or Upgrading to Argus Safety 7.0.3

Whether you are upgrading to Argus Safety 7.0.3 or installing a fresh instance of it, it will be necessary to generate new keys using the Cryptography Key Editor. The first step is to create or upgrade the database. After creating or upgrading the database, all application servers will need to be updated by copying the ArgusSecureKey.ini to their respective .\Windows folder.

### The Argus Safety 7.0.3 Database

Prior to creating a 7.0.3 database or upgrading to a 7.0.3 database, a new Cryptography Key needs to be generated using the Cryptography Key Editor. Running the Schema Creation tool prior to creating the key will inform the user that the cryptography key is required.

To generate a new Cryptography key, refer to the Generating a New Cryptography Key section.

You must also run the Argus Safety Schema Creation Tool to create or upgrade the database.

### The Argus Safety 7.0.3 Application Servers

After the application servers have been installed with 7.0.3, copy the ArgusSecureKey.ini file from the .\Windows folder of the system which was used to create or upgrade the database to the .\Windows folder of each installed application server.

### Generating a New Cryptography Key

Prior to running the Schema Creation tool the first time, it is necessary to generate a key file (ArgusSecureKey.ini) using the Cryptography Key Editor.

To create a new Cryptography Key, follow these steps:

1. Launch the Cryptography Key Editor. The Key Editor Utility screen appears.

2. Click New.

3. The following screen appears.

4. In the Note to be added as comment field, enter a comment that will be saved in the ArgusSecureKey.ini. This can be any form of metadata, such as why this key was generated or for what environments it is used.

5. In the Enter ARGUSUSER password field, enter the password for the database user called ARGUSUSER.

6. Confirm the password in the Confirm password field.

7. Click OK. The ArgusSecureKey.ini file gets created in the <Installation folder> \ CryptoKeyEditor\output\<DateTimeStamp>\.The Argus Secure Key Path dialog is displayed.

8. Click the link in the Argus Secure Key Path dialog to open the folder in Windows Explorer.

9. Click Close, I will copy it manually to close the dialog and copy the file manually from the window that gets opened by clicking on the link mentioned above (in step 9).

10. Click Copy to windows folder to move the generated ArgusSecureKey.ini file to the .\Windows folder.

## Resetting Password / Changing the Cryptography Key

This section lists the steps to perform the following tasks:

- Resetting the ARGUSUSER Password

- Editing Keys

- Re-encrypting Common User Passwords

- Generating Encrypted String from Clear Text on Configured User Cryptography Key

- Resetting the Environment if ArgusSecureKey.ini is Lost

### Resetting the ARGUSUSER Password

If the password for the database user "ARGUSUSER" has changed, you will need to reset the password in the ArgusSecureKey.ini file on all the servers.

Execute the following steps to reset the ARGUSUSER password:

1. Launch the Cryptography Key Editor. The Key Editor Utility screen appears.

2. Click Existing. The Key Editor Login or Re-encrypt ARGUSUSER screen appears.

3. In the Enter the ARGUSUSER password field, enter the password for the database user called ARGUSUSER.

4. Enter the name of the database in the Database name field.

5. Click Re-encrypt. The following dialog appears.

6. Click Yes.

7. Copy the updated ArgusSecureKey.ini File from the .\Windows folder to all the .\Windows folder of all the application servers.

8. Verify that you can login to the Argus Safety application.

### Editing Keys

An administrator might want to change a key due to various reasons like a policy to change key every few days, network compromise, etc.

Execute the following steps to edit the cryptography keys:

1. Launch the Cryptography Key Editor. The Key Editor Utility screen appears.

2. Click Existing. The Key Editor Login or Re-encrypt ARGUSUSER screen appears.

3. In the Enter the ARGUSUSER password field, enter the password for the database user called ARGUSUSER.

4. Enter the name of the database in the Database name field.

5. Click Login. The following Key Editor Options for Existing Installation screen appears.

6. Enter the DBA User Name and User Password.

7. Click Validate.

8. Check the Edit Key checkbox. This enables the child checkboxes of User Key and Cookie Key.

9. The User Key is used for all the encrypted strings which are persisted in the database or file server.

10. The Cookie Key is only used to encrypt and decrypt the key.

11. The user has the option to change either one or both keys.

12. Select the checkboxes in front of the key that you want to change.

13. Change the Key Size drop-down list value, if you wish to change the key size. Key Size is measured in bits of the key used in a cryptographic algorithm.

14. Click Re-Generate. This will change the value of the checked items and the new value will be visible in the textbox.

15. Click Execute. The Reason for this Action dialog is displayed, prompting the user to add a reason for his action.

16. The text entered here is visible in the Audit Log in the Argus Safety application.

17. Click OK.

18. Check the status box to verify if the operation has been successful.

19. If the operation is successful and the Cryptography key is checked, then the changed key is now stored in the ArgusSecureKey.ini. You should now copy this file from the .\Windows folder of the current machine and paste it to the .\Windows folder of all web servers.

20. When the user key is changed, all the encrypted strings in the database are re-encrypted using the new key. However, there are still some other file server locations where this key change must also be applied manually. The following is a list of places where the changes must be done manually:

21. Items to be changed from the User Interface:

22. Argus Services: Open Argus Safety Service Configuration: Open all the processes and enter password again

23. Cyclone: Open ESM Mapping utility and reenter Cyclone password

24. ESM Common User: Open ESM Mapping utility and reenter ESM Common user password

25. Re-enter the DBPassword in the configuration files, as explained in the following sections:

26. Point 2 of the RelsysWindowsService.exe.config sub-section

27. Point 5 of the Configuring the Dossier Application section

28. The Product License Study Interface section

### Re-encrypting Common User Passwords

The Key Editor Options for Existing Installation screen can also be used to change the common user (ARGUS_LOGIN, ARGUS_LOGIN_I, and ARGUS_LOGIN_IPS) passwords.

Execute the following steps to re-encrypt the common user passwords:

1. Launch the Cryptography Key Editor. The Key Editor Utility screen appears.

2. Click Existing. The Key Editor Login or Re-encrypt ARGUSUSER screen appears.

3. In the Enter the ARGUSUSER password field, enter the password for the database user called ARGUSUSER.

4. Enter the name of the database in the Database name field.

5. Click Login. The following Key Editor Options for Existing Installation screen appears.

6. Enter the DBA User Name and User Password.

7. Click Validate.

8. Check the Re-encrypt checkbox.

9. Enter the passwords for the common users.

10. Click Execute. The Reason for this Action dialog is displayed, prompting the user to add a reason for his action.

11. The text entered here is visible in the Audit Log in the Argus Safety application.

12. Click OK.

13. Check the status box to verify if the operation has been successful.

### Generating Encrypted String from Clear Text on Configured User Cryptography Key

Generate the encrypted string from clear text, using the configured UserCryptoKey in ArgusSecureKey.ini.

Execute the following steps to re-encrypt the common user passwords:

1. Launch the Cryptography Key Editor. The Key Editor Utility screen appears.

2. Click Existing. The Key Edit Login screen appears.

3. In the Enter the ARGUSUSER password field, enter the password for the database user called ARGUSUSER.

4. Enter the name of the database in the Database name field.

5. Click Login. The following Key Editor Options for Existing Installation screen appears.

6. Enter the DBA User Name and User Password.

7. Click Validate.

8. Check the Generate Encrypted checkbox.

9. Enter the password in the Clear text field.

10. Click Execute. The Reason for this Action dialog is displayed, prompting the user to add a reason for his action.

11. The text entered here is visible in the Audit Log in the Argus Safety application.

12. Click OK.

13. Check the status box to verify if the operation has been successful. If the operation is successful, the encrypted script gets displayed in the Encrypted String field.

### Resetting the Environment if ArgusSecureKey.ini is Lost

This section lists the steps to be followed in resetting the environment if the ArgusSecureKey.ini is lost. In such a scenario, execute the following steps:

1. Follow the steps listed in the Resetting the ARGUSUSER Password section to generate a new key and copy it to the Windows folder.

2. Follow the steps listed in the Re-encrypting Common User Passwords section to re-encrypt common user passwords.

3. Re-encrypt strings in the following locations:

4. LDAP: Clear column LDAP_SEARCH_PASSWORD in all rows from table CFG_LDAP_SERVERS. Now open Argus Console -> System Configuration -> System Management -> LDAP and re-enter passwords for all configurations

   SMTP: Clear column USER_PASSWORD in all rows from table CFG_SMTP. Now open Argus Console -> System Configuration -> SMTP Configuration and re-enter passwords for SMTP account

   Documentum: Clear column VALUE for row where SECTION='SYSTEM' AND KEY='DOCUMENTUM_PASSWORD' from table CMN_PROFILE_ENTERPRISE. Now open Argus Console -> System Configuration ->Common profile Switches to re-enter Documentum password

   Argus Services: Open Argus Safety Service Configuration: Open all the processes and enter password again

   Cyclone: Open ESM Mapping utility and re-enter the Cyclone password

   ESM Common User: Open ESM Mapping utility and re-enter the ESM Common User password

   Re-enter the DBPassword in the configuration files, as explained in the following sections:

5. Point 2 of the RelsysWindowsService.exe.config sub-section

6. Point 5 of the Configuring the Dossier Application section

7. The Product License Study Interface section