Threat Manager lets administrators change passwords for its components and configure SSL mode. Both are handled by the setup.sh script installed during provisioning or upgrade.

iManage Threat Manager must be restarted to complete this procedure. Before starting, locate the folder where Threat Manager was deployed. The setup.sh script is installed during Provisioning the iManage Threat Manager OVA or Upgrade.

Task: Change Threat Manager component passwords

Follow this procedure to change passwords for one or more Threat Manager components, and to configure SSL mode if required.

Threat Manager allows you to change passwords for the following components:

  • ActiveMQ Console

  • Analytics Cache (Redis)

  • MongoDB

Phase 1: Run the setup script

Use the setup.sh script to begin configuration:

  1. Browse to the folder where Threat Manager was deployed.

  2. Run the following command: ./setup.sh

Phase 2: Configure SSL mode

The script prompts you to run iManage Threat Manager in SSL mode. If SSL is already enabled, the script asks whether you want to change the configuration.

If you choose to enable SSL mode, supply valid certificate files or allow the script to generate a self-signed certificate.

NOTE: A self-signed certificate is appropriate only for proof-of-concept (POC) or demonstrations, and will generate a browser warning.

Phase 3: Reset component passwords

The script prompts you to reset the password for each component:

Password for <Component Name> is already set. Do you want to reset it? [Y,n]

  • Type Y to update the password for that component.

  • Type n to skip.

NOTE: These entries are case-sensitive.

After typing Y, enter and confirm the current password, then enter the new password.

Phase 4: Restart Threat Manager

When all password changes are complete, restart the Threat Manager stack:

  1. Run the following command to stop the Threat Manager stack: docker stack down tmstack

  1. Wait approximately 30 seconds, then run the following command to verify that all components have stopped: docker ps. No containers should be displayed.

  2. When all components are stopped, run the following command: docker stack deploy --compose-file ./docker-compose_v10.yaml --with-registry-auth tmstack

Any password changes that you've made are now set and applicable in Threat Manager.