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
Remote Access VPN Configuration - Cisco FTD RSA Ready SecurID Access Implementation Guide Number of Views FortiGate Firewall - RADIUS Configuration Using SSL VPN - RSA Ready Implementation Guide Number of Views FortiGate Firewall - Configure RADIUS Authentication Manager Using SSL VPN - RSA Ready Implementation Guide Number of Views High CPU usage in Juniper VPN - RSA Authentication Manager Number of Views Radius Client Authentication failed For PIN+Token profile (New PIN Mode) with Cisco Anyconnect VPN Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
