Enable RADIUS debug/verbose logs with all versions of RSA Authentication Manager 8.x
Originally Published: 2012-04-09
Last Modified: 2026-01-14
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Issue
Resolution
For Authentication Manager 8.5.x and below, RSA uses Steel Belted RADIUS. For 8.6 and higher, we use Free RADIUS. Because of these changes, the way debug is enabled has changed slightly. Follow the steps below. For all versions, changes are done from the Operations Console, although you can edit the files in /opt/rsa/am/radius.
- Select Deployment Configuration > RADIUS Servers > Edit RADIUS Server.
- Click the drop down arrow on the primary Authentication Manager server and choose Manage Server Files.
For Authentication Manager 8.5 and below
- Click on the drop down arrow next to the radius.ini file and choose Edit.
- Uncomment the following three lines: [Configuration], Trace Level and Log level, by removing the semicolon ( ; ) or # sign from the beginning of the line.
- Change the trace level and log level values to 2 (accepted values are only 0,1,2), as shown:
[Configuration]
LogLevel = 2
TraceLevel = 2
- When done, click Save & Restart RADIUS Server. This restart allows the debug changes to take effect.
For Authentication Manager 8.6 and higher
- Click on the drop down arrow next to the radiusd.conf file and choose Edit.
- Change the debug_level value to 2, as shown:
debug_level=2
- When done, click Save & Restart RADIUS Server. This restart allows the debug changes to take effect
- When RADIUS testing is complete, turn off RADIUS debug logging by following the steps above, changing LogLevel and TraceLevel or debug_level back to 0 then restarting RADIUS servers.
RADIUS logs are found in /opt/rsa/am/radius on their respective servers.
- For Authentication Manager 8.5 and below, the files are named mmddyyyy.log (often called date.log files), where the date is the day they were written.
- In Authentication Manager 8.6 and above, the log files are in the same directory, but it is called radius.log.
Related Articles
RADIUS shared secret limitations of RADIUS clients configured with RSA Authentication Manager 759Number of Views Adding a Palo Alto RADIUS dictionary to RSA RADIUS for RSA Authentication Manager 8.x 816Number of Views RSA Authentication Manager 8.x fails to process RADIUS authentication requests from NPS 45Number of Views How to decrypt RADIUS traffic using Wireshark with RSA Authentication Manager 380Number of Views How to Enable RADIUS Debug and Verbose Logs in RSA Authentication Manager 8.6 and Later 155Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?