Strategy JSP Web and Mobile 2021 Update 4 and above:
- Open the log4j2.properties file under WEB-INF/classes and configure property.filename to an absolute path for forward slash. For example:
property.filename = C:/samlLOG/test.log
- The log file will be generated under the path defined in the property.filename parameter.
Change the level of org.opensaml, that is the logger.d.level property, to debug and leave everything else as the default. This generates a clean log with all SAML messages, along with any errors or exceptions.
logger.d.name = org.opensaml
logger.d.level = debug
- Restart the Web Server.
Strategy JSP Web and Mobile 2019 – 2021 Update 3:
- Open the log4j.properties file under WEB-INF/classes and configure the log4j.appender.SAMLAppender.File to an absolute path with forward slash. For example:
log4j.appender.SAMLAppender.File=C:/samlLOG/test.log
The log file will be generated under the path defined in the log4j.appender.SAMLAppender.File parameter.
- Configure log4j.logger.PROTOCOL_MESSAGE to DEBUG and leave all the other loggers as default. Depending on the specific issue, different loggers can be configured.
log4j.logger.PROTOCOL_MESSAGE=DEBUG
- Restart the Web Server.
Strategy JSP Web and Mobile 10.6 - 11.0:
- Copy the log4j.properties file from WEB-INF/classes/resources/SAML/stage to WEB-INF/classes.
- Open the log4j.properties file under WEB-INF/classes, and configure log4j.appender.SAMLAppender.File to an absolute path with forward slash, e.g.
log4j.appender.SAMLAppender.File=C:/samlLOG/test.log
The log file will be generated under the path defined in the log4j.appender.SAMLAppender.File parameter.
- Generally, it is recommended to configure log4j.logger.PROTOCOL_MESSAGE to DEBUG and leave all the other loggers as default. Depending on the specific issue, different loggers could be configured.
log4j.logger.PROTOCOL_MESSAGE=DEBUG
- The changes will take effect after the web server is restarted.
