How long can an Agent wait to send a next tokencode or new pin message?
Originally Published: 2006-09-15
Article Number
Applies To
User waits more than 2 minutes 20 seconds to send requested data after receiving a NEXT_TOKENCODE_REQUIRED or NEW_PIN_REQUIRED status from the Authentication Manager.
Issue
The Authentication Manager ignores the provided tokencode or PIN value.
Cause
Resolution
Related Articles
RSA SecurID end users setting their own PIN or next tokencode on a VPN connection Number of Views Review action has been performed on a review that is in 'Completed' in RSA Identity Governance & Lifecycle Number of Views Entitlements manually added when an Application has 'Complete Manual Activity Before Collection' enabled are not removed w… Number of Views Entitlements manually added when an Application has 'Complete Manual Activity Before Collection' enabled do not show in th… Number of Views enVision users need a folder where network users can access saved queries. Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA-2026-10: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide RSA SecurID Software Token 4.2.1 for Mac OS X Administrator's Guide
Don't see what you're looking for?
