Configure verbose logging
When troubleshooting its often beneficial to include the logging level to verbose.
During this task we will specify a logging level of verbose.

Specifying a verbose logging level can cause log file size to increase quickly. Okta recommends that once the problem has been diagnosed that the log level be reset to its original value.
- On the system running the Agent, navigate to the Okta On-Prem MFA Agent install directory.
By default, this is C:\Program Files (x86)\Okta\Okta On-Prem MFA Agent\current\user\config\rsa-securid - Using a text editor, open log4j2.xml.
- Modify the line <Root level="info">, changing info to trace.
- Save your changes.
- Restart the Okta On-Prem MFA Agent Service using the Windows Administrative tools.
Before making changes to log4j2.xml, Okta recommends creating a backup.
When complete the updated file should resemble:
<xml version="1.0" encoding="UTF-8"> <Configuration status="error" name="OktaOnPremMFAAgentLogConfig"> <Appenders> <Console name="STDOUT" target="SYSTEM_OUT"> <PatternLayout> <Pattern>%d{yyyy-MM-dd HH:mm:ss}{UTC} (UTC) %5p - %m%n</Pattern> </PatternLayout> </Console> <RollingFile name="logfile" fileName="logs/Agent.log" filePattern="logs/Agent.log.%i"> <PatternLayout> <Pattern>%d{yyyy-MM-dd HH:mm:ss}{UTC} (UTC) %5p - %m%n</Pattern> </PatternLayout> <Policies> <SizeBasedTriggeringPolicy size="5 MB"/> </Policies> <DefaultRolloverStrategy max="9"/> </RollingFile> </Appenders> <Loggers> <Logger name="org.tinyradius.util" level="off" additivity="false"> <AppenderRef ref="STDOUT"/> <AppenderRef ref="logfile"/> </Logger> <Root level="trace"> <AppenderRef ref="STDOUT"/> <AppenderRef ref="logfile"/> </Root> </Loggers> </Configuration>