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 New PIN and next Tokencode modes fail when dialing through a Cisco NAS Number of Views RSA SecurID end users setting their own PIN or next tokencode on a VPN connection Number of Views Error: '103: Invalid Browser State. Either your browser does not support HTTP Cookies or you took too long to respond to t… Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager 8.9 Release Notes (January 2026) How to create and configure certificates for HTTPS access when using intermediate CA certs in RSA Identity Governance & Li… Authentication Manager Supported Hardware and Upgrade Paths
Don't see what you're looking for?
