ODA (on demand access) token.will not authenticate when connecting thru a Netscaler VPN Gateway
Originally Published: 2015-03-30
Last Modified: 2023-09-25
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1.0
Platform: Linux
Platform (Other): null
O/S Version: null
Product Name: null
Product Description: null
Issue
Cause
When the authentication request with the PIN was sent to the primary, the RADIUS challenge for the next tokencode was being sent to the Netscaler.
The Netscaler sent the next authentication request with the tokencode in reply to the RADIUS challenge to the replica configured for load balancing.
We removed the load balancing configuration and ODA started to work correctly
Resolution
Related Articles
RSA Via Lifecycle and Governance/Aveksa server will not start after environment customization Number of Views AFX Server on a WildFly cluster fails to start with 'Cannot connect to RSA Identity Governance and Lifecycle. The watchdog… Number of Views RSA SecurID Access identity router will not start after reboot on Microsoft Hyper-V Number of Views Replica Radius server will not synchronize, Primary status is listed as Standalone Number of Views Services will not start after changing IP address of RSA Authentication Manager 8.x from command line Number of Views
Trending Articles
Troubleshooting RSA MFA Agent for Microsoft Windows RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console Deploy an Identity Router Virtual Machine in Microsoft Azure How to Change the Token Lifetime Extension Window in Authentication Manager Using rsautil
Don't see what you're looking for?
