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
Cisco Router with IOS 12.2(2)XB/12.2(4)T or later unable to handle New PIN Mode and Next Tokencode Mode Authentications th… Number of Views Users cannot authenticate successfully when the RSA SecurID token is in either Next Tokencode Mode or New PIN Mode when au… Number of Views 'Request could not be handled' error reverting a Role that has been moved to a different Role Set in RSA Identity Governan… Number of Views Entitlements manually added when an Application has 'Complete Manual Activity Before Collection' enabled are not removed w… Number of Views RSA Authentication Manager and Self-Signed Certificates Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service LDAP password authentication failed - Logon failure: unknown username or invalid password when attempting RADIUS authentic…
Don't see what you're looking for?
