Enable debug level logging for troubleshooting SAML

Last Updated : Mar 28, 2022 |
Prolog information
Metadata
Keywords:
Use this procedure to enable debug level logging to troubleshoot SAML.
Before you begin
SAML must be enabled.
  1. Log in to the Cluster Control Manager (CCM) console as the customer user.
  2. Switch to being the root user by entering the command su.
  3. To list the Historical reporting pods, use the following command:
    ADDITIONAL INFORMATION:
    sudo kubectl get pods --namespace mstr
  4. To enter into the mstr-web pod, use the following command:
    ADDITIONAL INFORMATION:
    sudo kubectl exec -it --namespace mstr mstr-web-podNumber -- /bin/bash
  5. The SAML logs are in the /opt/tomcat/logs/SAML/ directory.
  6. Edit the SAML logging properties file on the following path:
    ADDITIONAL INFORMATION:
    vi /opt/tomcat/webapps/AvayaAnalytics/WEB-INF/classes/log4j2.properties
  7. Change SAML loggers to debug level. For example, auth.saml and opensaml.
    ADDITIONAL INFORMATION: logger.b.name = .auth.saml
    logger.b.level = debug
    logger.d.name = org.opensaml
    logger.d.level = debug
  8. Click Save and close.
  9. To restart the web server process, use the following command:
    ADDITIONAL INFORMATION:
    /opt/tomcat/bin/shutdown.sh
  10. To confirm the process is stopped and restarted, use the following command:
    ADDITIONAL INFORMATION:
    ps -ef | grep tomcat
  11. Repeat steps 6 through 10 to change the log level to error.
    ADDITIONAL INFORMATION: logger.d.name = org.opensaml
    logger.d.level = error