ODA (on demand access) token.will not authenticate when connecting thru a Netscaler VPN Gateway
Originally Published: 2015-03-30
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
iPlanet Web Server will not install when 'nobody' is selected as the system user Number of Views What is process on moving files encrypted by FSM to another system? Number of Views Replica will not Authenticate Multiple Authentications Number of Views How many levels of Sub-CA chaining are supported in Sentry CA 3.x? 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
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?
