After upgrading RSA Authentication manager to version 8.6, users AnyConnect are not able to authenticate
Originally Published: 2021-09-23
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.6.0
Platform: null
Platform (Other): null
O/S Version: null
Product Name: null
Product Description: null
Issue
Cause
Resolution
To Turn on Verbose logging. Go to the Operations Console->Deployment Configuration->Radius Servers. Select your Primary AM server in the dropdown menu
Select Manage Server Files, edit radiusd.conf. Increased radius logging from debug_level=0 to debug_level=2
Workaround
In the Radius client list., if you see any more Radius clients with Make/Model set to Cisco PIX FW. change them too
Related Articles
RSA Authentication Manager 8.x services won't start when network interface adapter eth0 is not found Number of Views RSA Via Lifecycle and Governance User Interface is inaccessible after rebooting an Appliance with the error "This page can… Number of Views Team Password Manager - SAML Relying Party Configuration - RSA Ready Implementation Guide Number of Views Team Password Manager - SAML My Page SSO Configuration - RSA Ready Implementation Guide Number of Views How to contact the RSA Ready team with questions Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager 8.9 Setup and Configuration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings.
Don't see what you're looking for?
