Incorrect passcode under certain conditions from CA Siteminder to RSA Authentication Manager 8.x
Originally Published: 2015-04-30
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Issue
- User lockout is set to four incorrect passcodes.
- If testing with the CA Siteminder and three bad tokencodes are given, the user is now set to Next Tokencode Mode.
- The CA Siteminder does not relay that the user is in Next Tokencode Mode to the user.
- The next time the user tries to login and gives the correct passcode, the CA Siteminder sends an incorrect passcode message to Authentication Manager and gives the user the message that they are in Next Tokencode Mode and to input the next tokencode.
- Because the site was set up for four incorrect passcodes to lock a user, the user is now locked.
- This works as documented for various RSA Authentication Agents (Windows, PAM, etc.)
- It is only the CA Siteminder that appears to do this.
Cause
Resolution
Workaround
Related Articles
What Ports are used by enVision Number of Views How to close ports used by the RSA Authentication Agent to block SSLv3 communication to RSA Authentication Manager 8.x Number of Views How to perform bulk action on review items greater than 10k in RSA Via Lifecycle and Governance 6.9.1 Number of Views The RSA SecurID Access Cloud Authentication Service rejects signed SP-initiated SAML requests with an HTTP Redirect binding Number of Views Update to RSA Authentication Manager Security Patching Process Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to Download OTP Token Seed Files from myRSA Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
