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 Via Lifecycle and Governance User Interface is inaccessible after rebooting an Appliance with the error "This page can… Number of Views Self-Service Console doesn't display On-Demand Authentication (ODA) link for RSA Authentication Manager 8.x Number of Views Can't Attach RSA Authentication Manager 8.1 replica when Primary has migrated data. Number of Views RSA Authentication Manager 8.x services won't start when network interface adapter eth0 is not found Number of Views Team Password Manager - SAML Relying Party Configuration - RSA Ready Implementation Guide Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
