How long can an Agent wait to send a next tokencode or new pin message?
Originally Published: 2006-09-15
Last Modified: 2023-10-06
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 Identity Governance and Lifecycle 7.5 Installation Guide Number of Views RSA Identity Governance and Lifecycle 7.2.1 Installation Guide Number of Views Cloud Administration FIDO Authenticator API Number of Views RSA Identity Governance and Lifecycle 7.1 Installation Guide Number of Views How to overcome database connection failure for Postgres DB collectors in RSA Via Lifecycle and Governance Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn… How to manually sync a replica in an RSA Authentication Manager 8.x deployment with one or more replicas
Don't see what you're looking for?
