Encrypting connections in non-FIPS 140 mode

applications that are based on Foundation 9.1 or later software, and running in non-FIPS 140 mode use TLSv1.2 encrypted connections by default. For applications that are based on pre-9.1 Foundation software, the encrypted connections are configured by using the two environment variables, and .

Note: These environment variables are ignored if the communicating applications are TLS-capable, but are honored when a TLS-capable application is interacting with a non-TLS-capable application.

To set the environment variables so that they can be used by the programs of an Smart Assurance product, edit the runcmd_env.sh file, which is located in the BASEDIR/smarts/local/conf directory of that product.

Procedure

1. Go to the BASEDIR/smarts/bin directory and enter the following command to open the runcmd_env.sh file:
   sm_edit conf/runcmd_env.sh
2. Review the contents of the file. The default values for the SM_INCOMING_PROTOCOL and SM_OUTGOING PROTOCOl are 1 and 0.
   SM_INCOMING_PROTOCOL=1,0
   SM_OUTGOING_PROTOCOL=1,0
3. Update the values for the variables to meet the needs of your system.
   To raise security to the next highest level, change 1 to 2:
   SM_INCOMING_PROTOCOL=2,1,0
   SM_OUTGOING_PROTOCOL=2,1,0
4. Save and close the file.
   The modified version of the runcmd_env.sh file is saved to the BASEDIR/smarts/local/conf directory.
5. Restart the Manager if applicable.