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 Exporting a set of One Time Tokencodes from RSA Authentication Manager Self-service Console Number of Views Invalid tokencode failures and expired QR code alerts in RSA SecurID Authenticate app Number of Views Offline Authentication Policy Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
