RSA SecurID On-Demand Authentication (ODA) requires submitting the token within two minutes or 120 seconds after the PIN is submitted
Originally Published: 2015-03-03
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Issue
This is the currently functioning as designed.
Resolution
- Educate users that they need to submit the token within two minutes of requesting it.
- A somewhat cumbersome option is that after the user submits the user ID and PIN then receives the tokencode, abandon the login session entirely, and create a new authentication session. Since the token is good for 60 minutes, the user logs in this second time with user ID and this time enters the tokencode.
Related Articles
Multi-App Entitlement Data Collector (MAEDC) fails with ORA-30926 if two MAEDCs overlap in Application Name and Internal I… Number of Views updateReviewItems web service fails to update review items when the UserID is the same for two users in RSA Identity Gover… Number of Views Cisco ACS / ASA sends two requests to Authentication Manager 8.x Number of Views Unable to integrate two RSA Authentication Agents for Windows on the same server (Node Verification Mismatch) Number of Views Applying two-factor authentication with the RSA Authentication Agent for PAM to the GNOME screensaver found in the GNOME d… Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
