Cisco VPN client and error 413 (user authentication failed) with RSA SecurID

I have an ASA 5510 that I use to provide VPN access to my HQ network.  The authentication for the VPN users is handled by an RSA SecurID appliance.  Ever since we started using SecurID for auth (we previously used AD) we've had some issues with the auth failing if you try to connect more than once.

For example, if I connect to VPN it works fine, but if I disconnect and attempt to reconnect, it immediately gives me error 413 - user authentication failed.  If I close the VPN client and relaunch it, it will work again.  This also happens if I launch the VPN client, click connect, press cancel when it prompts for auth, and then click connect again...instead of prompting for auth, it immediately says auth failed.   Again, closing and relaunching the VPN client is all that is needed to resolve the issue, but a lot of our users don't think to try this, so it leads to a lot of calls to the helpdesk.

If we use AD for auth, this problem goes away, so it must be something to do with the SecurID system and the way the ASA talks to it.  We're running version of the Cisco IPSec VPN client, and the same problem also occurs with version 4.6.  We use the SDI auth protocol between the ASA and SecurID appliance.  We have support agreements for both devices, but Cisco and RSA each say the problem is with the other device.
Who is Participating?
cartoonbabeConnect With a Mentor Commented:
We had the 413 error problem using Cisco VPN version 5.0.0 and versions 4.6 and 4.7.  Cisco recommended we move to version  That was only part of the solution.  The ASA 5540 concentrators also had to be upgraded to 8.0.4 code.  That eliminated the problem.  What you are describing is exactly what we experienced.  The 413 error appeared when you clicked connect.  Didn't even get prompted for a login and that error message appeared.
at my company I know each SecurID OTP changes every minute and can ONLY be used once per minute.  Does your ID change to a different OTP when you log in again?  Try waiting until the OTP changes again without relaunching the client.

you still may want to check your SecurID settings though to see if something is set so you're only allowed to login so many times within a certain amount of time.
FWestonAuthor Commented:
Sorry, I guess I wasn't clear.  It does this even if I cancel the connect before putting in a password and then try to reconnect.  The ASA shouldn't even be sending a request for AAA authentication to the SecurID appliance yet, so it's gotta be some kind of Cisco/SDI issue..
what do the logs on the ASA say when you move it to debug level and repeat the process.  Sounds like it gets cached.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.