After upgrading RSA Authentication manager to version 8.6, users AnyConnect are not able to authenticate
Originally Published: 2021-09-23
Last Modified: 2023-09-22
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
Performance improvements related to T_AV_MODEL_EXPLODEDUSERENTS table in RSA Identity Governance & Lifecycle 50Number of Views RSA Authentication Manager 8.x services won't start when network interface adapter eth0 is not found 265Number of Views Can't Attach RSA Authentication Manager 8.1 replica when Primary has migrated data. 470Number of Views The approval workflow isn't working as expected when grouping by business source in the request form with the provisioning… 33Number of Views How to obtain the version information for RSA Authentication Agent for PAM installed on Linux 411Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?