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… 27Number of Views Users cannot authenticate successfully when the RSA SecurID token is in either Next Tokencode Mode or New PIN Mode when au… 98Number of Views New PIN and next Tokencode modes fail when dialing through a Cisco NAS 55Number of Views Exporting a set of One Time Tokencodes from RSA Authentication Manager Self-service Console 96Number of Views Assign a Temporary Fixed Tokencode for Online Emergency Access 100Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 Downloading RSA Authentication Manager license files or RSA Software token seed records Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager Patch Updates RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide
Don't see what you're looking for?