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 .
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.
runcmd_env.sh
file, which is located in the
BASEDIR/smarts/local/conf
directory of that product. - Go to theBASEDIR/smarts/bindirectory and enter the following command to open theruncmd_env.shfile:sm_edit conf/runcmd_env.sh
- Review the contents of the file. The default values for theSM_INCOMING_PROTOCOLandSM_OUTGOING PROTOCOlare 1 and 0.SM_INCOMING_PROTOCOL=1,0SM_OUTGOING_PROTOCOL=1,0
- 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,0SM_OUTGOING_PROTOCOL=2,1,0
- Save and close the file.The modified version of theruncmd_env.shfile is saved to theBASEDIR/smarts/local/confdirectory.
- Restart theManagerif applicable.