Debug logging for SAML
- Last Updated: May 29, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Due to variations in how different vendors implement roles, you may need to troubleshoot
your SAML configuration when issues occur. Enabling debug-level logging is a useful
starting point for diagnosing SAML-related problems.
-
Open instance/ablapps/abl-app-name/conf/logging-ablapp.xml.
- Add the following logger entries:
<logger name="org.springframework.security.saml2" level="DEBUG"/> <logger name="org.opensaml" level="DEBUG"/> <logger name=" PROTOCOL_MESSAGE " level="DEBUG"/> - Save the file.
- Restart the application server for the changes to take effect.
Result:
The application server generates detailed SAML processing and protocol message information in the logs. Use this information to identify and troubleshoot configuration or integration issues with your SAML identity provider.