New PIN Mode and Next Tokencode Mode fail after Cisco ASA upgrade to 9.1.7 in RSA Authentication Manager 8.x
Originally Published: 2016-04-07
Last Modified: 2026-06-09
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Platform (Other): Cisco ASA
O/S Version: ASA 9.1.7
Issue
- Users are unable to set PINs for tokens.
- Authentication failures when the next tokencode is entered.
Passcode format error and authentication failure
On the Cisco client, the error is:
Session operation failure processing request from agent
Resolution
This is Cisco bug CSCuy89425 (AAA: RSA/SDI unable to set new PIN), and it occurs with the RSA SecurID_Native protocol.
Possible workarounds include:
- Switch to RADIUS protocol (as per the RSA SecurID Access Implementation Guide for the Cisco Adaptive Security Appliance (ASA).
- Authenticate from the Self-Service Console when a token is in New PIN Mode or Next Tokencode Mode.
For more details on how to resolve the issue for a Cisco VPN client or iPhone, review documentation for CSCuy89425 (AAA: RSA/SDI unable to set new PIN).
Related Articles
How to enable RSA SecurID protection on Microsoft Outlook Web Access (OWA) Exchange ActiveSync (EAS) and Microsoft Outlo… Number of Views RSA SecurID Software Token 2.4 for iOS Quick Start (Spanish) Number of Views RSA SecurID Software Token 2.4 for iOS Quick Start (French) Number of Views Radius Client Authentication failed For PIN+Token profile (New PIN Mode) with Cisco Anyconnect VPN Number of Views Error "PIN change failed dictionary check" and authentication fails for a user in new PIN mode in RSA Authentication Manag… Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide 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 Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console Unable to Resolve User by Login ID and/or Alias or Authenticator Not Assigned to User When Attempting to Authenticate via …
Don't see what you're looking for?
