Out of support This documentation supports the 8.0 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.Click here to view the documentation for a supported version of Remedy Single Sign-On.

Using BMC Atrium Single Sign-On for logging


Many logging attributes of BMC Atrium Single Sign-On are configurable through the administrator console. Many attributes can be customized. The attributes that are commonly modified are:

  • Maximum log file size (default 100,000,000 bytes)
  • Number of history files (1 file)
  • Log file location (default): <installationDirectory>/tomcat/webapps/atriumsso/WEB-INF/config/atriumsso/log
  • Logged data attributes

There are additional attributes that can be configured, for example, signing the logs or changing logging information storage from file format to a database table.

To modify logging attributes

  1. Navigate to Configuration > System > Logging link
  2. Configure the logging attributes.
  3. Click Save.

For more information on logging parameters, refer to the OpenSSO documentation.

To enable detailed logging

  1. Navigate to the Debugging page: Configuration > Servers and Sites > serverLink > General
  2. In the Debugging section, select your logging level from the drop down menu.
    • Error (default) The logging level is typically kept at this default.
    • Message generates the most verbose logs but severely impacts server performance. Message level should only be used when an issue is being worked on. 

      Note

      BMC recommends that for normal operation, set the Debugging level to either Off or Error.

  3. Click Save.
  4. Restart the server for the logging changes to take effect.

To modify the rsa_api.properties file

For RSA SecurID, additional debug logging is available by modifying the rsa_api.properties file.

  1. Navigate to <installationDirectory>/tomcat/webapps/atriumsso/WEB-INF/config/atriumsso/auth/ace/data
  2. Edit the rsa_api.properties file.
  3. Change the RSA_ENABLE_DEBUG property from NO to YES.
     Changing this property increases the volume of debugging information supplied by the RSA SecurID module.
  4. Access the rsa_api_debug.log file in the debug logging directory for this information.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*