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
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 In RSA Identity Governance & Lifecycle, duplicate entries are created when a user switches between two Identity Data Colle… Number of Views Unable to remove account from group through a review in RSA Identity Governance & Lifecycle Number of Views RSA Authentication Manager 8.1 Security Configuration Guide Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
