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
RSA Via Lifecycle and Governance/Aveksa server will not start after environment customization Number of Views Replica will not Authenticate Multiple Authentications 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
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device SecurID Tokens How to implement SAML SSO Authentication with Microsoft Azure Active Directory and RSA Identity Governance & Lifecycle Do TCP Agent using API ver. 8.5 & 8.6 need a new sdconf.rec file after a new Primary is promoted? RSA Authentication Manager 8.9 Patches and Hotfixes Readme
Don't see what you're looking for?
