Monitoring FIPS-140 and normal mode conversions
The conversion task communicates through the BMC Atrium Single Sign-On log file (for example, atsso.0.log ). The log file contains messages to signify the start of the conversion, any errors, and the completion of the process. See Managing BMC Atrium Single Sign-On logging.
Using the default installation locations as an example, the log file is located at:
- (Microsoft Windows ) C:\Program Files\BMC Software\AtriumSSO\tomcat\temp
- (UNIX ) /opt/bmc/AtriumSSO/tomcat/conf
Conversion to FIPS-140 mode messages
Before starting the conversion, the background task validates that the JVM has been correctly modified and is capable of running in FIPS-140 mode. If the JVM test fails, the task logs an error message indicating the JVM inadequacies and the conversion aborts.
In addition, when BMC Atrium Single Sign-On is installed on an external Tomcat server, the background task verifies that the required Tomcat server and JVM configuration files exist.
When starting the conversion to FIPS-140 mode, the initial message displayed is:
BMCSSG1599I=Switching Atrium SSO server to FIPS-140 mode
When the conversion process successfully finishes, it posts this message:
BMCSSG1601I=Switch of Atrium SSO server to FIPS-140 mode completed
After saving the configuration change, the conversion process alters the encrypted data within the server. Until the process completes, BMC recommends that you monitor the security page in case the process fails.
Conversion to normal mode messages
When starting the conversion from FIPS-140 mode to normal mode, the initial message displayed is:
BMCSSG1598I=Switching Atrium SSO server to normal mode (not FIPS-140 mode)
When the conversion process successfully finishes, it posts this message:
BMCSSG1600E=Switch of Atrium SSO server to normal mode completed