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
Cisco ACS / ASA sends two requests to Authentication Manager 8.x Number of Views In RSA Identity Governance & Lifecycle, duplicate entries are created when a user switches between two Identity Data Colle… 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 How to configure more than two IP addresses for an RSA Authentication Manager 8.2 Web Tier Virtual Host Number of Views Multi-App Entitlement Data Collector (MAEDC) fails with ORA-30926 if two MAEDCs overlap in Application Name and Internal I… Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?
