000024994 - Cisco VPN Client not processing new pin required authentication response

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000024994
Applies ToCisco VPN Client 5.0.01
Cisco VPN Client 5.0.010.xx

Cisco Systems VPN Client Version


Secure VPN Connection terminated locally by the Client.
Reason 413: User Authentication Failed

Client error: Error 413
The Token Code  is entered correctly through the CISCO VPN Client v5.x for a user requesting SecurID authentication for the first time. However, when a  New PASSCODE is required prompting does not work or when (PIN + Tokencode) is entered, the user fails authentication.
Access denied new pin deferred.
Tested Versions
IssueCisco VPN Client fails with new pin mode or Next Token Code Mode.
ResolutionCisco VPN Client v June 29th, 2009
Cisco VPN Client v  March 27, 2008
See the latest RSA SecurID Ready implementation guide here.
Cisco VPN Client V 5.0.04 March 9, 2009
Tested versions as of  February 19th 2008 are 4.6, 4.8, and
See the latest RSA SecurID Ready implementation guide here.
NotesProblems experienced with CISCO VPN Client 4.x upgrades other than 4.6 & 4.8 that have problems or later versions (I.E. 5.x) must be reported to the CISCO Technical Assistance Center (TAC). CISCO recommends upgrading to VPN client 5.0.05 or higher.
Please refer CISCO hardware and software support requests go to the CISCO Technical Assistance Center (TAC). Contact information is available on CISCO's web site at http://www.cisco.com/en/US/support/index.html.
RSA Partner Information Guide:

Cisco VPN Client.  This is the original.



Cisco AnyConnect VPN client


Legacy Article IDa38772