- Knowledge Base
- Authenticators ("Tokens")
-
General Support
-
Technical Guides
-
SurePassID Authentication Server
-
Authenticators ("Tokens")
-
Windows Logon Manager (WLM)
-
ADFS Adapter
-
SAML2 IdP
-
LDAP
-
Self Service Portal (SSP)
-
LDAP Gateway
-
FIDO2/WebAuthn
-
License Management
-
Third Party Integrations
-
Twilio
-
Announcements and Alerts
-
Office 365
-
SurePassID VLE
What can cause a soft or hard token to be disabled?
A token can become disabled if the following occurs:
-
If the max number of consecutive failed OTPs (default is 10 times) is exceeded.
-
An admin disables it.
-
The token is marked as new and has not been activated which changes the status to enabled.
-
The above is not related to a token becoming disabled but will still mean that the token cannot be used for OTPs or sign on processing until it is activated via the activation process or the Self-Service Portal, or an admin changes the status to enabled.
-