AnsweredAssumed Answered

adaptive authentication invalid padding

Question asked by Ronald Rozensky on May 17, 2016
Latest reply on Jan 24, 2018 by Patrick Wong

Like • Show 0 Likes0
Comment • 5

receiving the following error message in RSA AA 7.1:

2016-05-16 16:16:25,368 ERROR [http-apr-8080-exec-4] [fff7-:da0463bb451:862a92d-] [] [com.rsa.csd.security.impl.DeviceTokenImplv6] - <Couldn't decrypt/unwrap device token: PMV65x4VT2YORnC7QWba9TzbCAnqLA9k0Sy1lfwp8CKlKy5qTYKPEvOqwTLFka0As/pdSaV7iYcWqD6PBV21VDA4h/MA== with msg: java.lang.RuntimeException: java.lang.RuntimeException: javax.crypto.BadPaddingException: Invalid padding.>

java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: javax.crypto.BadPaddingException: Invalid padding.

at com.passmarksecurity.security.InternalAppCrypt.decrypt(InternalAppCrypt.java:205)

at com.passmarksecurity.security.InternalAppCrypt.decrypt(InternalAppCrypt.java:90)

No changes to Java before this occurred. Deployed new crypto libraries per instructions from RSA support.

1 person has this question

Outcomes

Farshad Mahjoubi

May 31, 2016 2:23 PM

HI Ron,

Please let us know if you experience this after your upgrade.

Regards,

Farshad

Actions

Ronald Rozensky @ Farshad Mahjoubi on May 31, 2016 2:47 PM

Farshad,

I remembered from an earlier support call with you that if any part of the c-config*.xml files have encryption this error would occur. I had our admins check the files and fix all the config files and the issue is gone.

Ron

Actions

Gadi Shpits

Jun 6, 2016 12:22 PM

The cookie is not url encoded as it should be, please verify the correct cookie value is sent.

If the cookie is url encoded that it can be either BSAFE or the cookie was generated by a different java provider jvm.

Actions

huan zhou Jan 15, 2018 7:38 AM

encryption enabled?

Actions

Patrick Wong Jan 24, 2018 2:51 PM

Hi Ronald - I saw this problem after an upgrade as well. In my case, it was users who had cookies in their browser that was encrypted with the key in the previous RSA application. So when the users logged in to the new RSA application, the key wasn't present so it was unable to decrypt the cookie. After the user logs into the new application, a new cookie is encrypted and saved on their browser so they won't generate the message again. Hope this helps.

Actions

5 Replies

Farshad Mahjoubi May 31, 2016 2:23 PM
Mark Correct
Correct Answer
HI Ron,

Please let us know if you experience this after your upgrade.

Regards,
Farshad
Like • Show 0 Likes0
Actions
- Ronald Rozensky @ Farshad Mahjoubi on May 31, 2016 2:47 PM
  Mark Correct
  Correct Answer
  Farshad,
  
  I remembered from an earlier support call with you that if any part of the c-config*.xml files have encryption this error would occur. I had our admins check the files and fix all the config files and the issue is gone.
  
  Ron
  Like • Show 0 Likes0
  Actions
Gadi Shpits Jun 6, 2016 12:22 PM
Mark Correct
Correct Answer
The cookie is not url encoded as it should be, please verify the correct cookie value is sent.
If the cookie is url encoded that it can be either BSAFE or the cookie was generated by a different java provider jvm.
Like • Show 0 Likes0
Actions
huan zhou Jan 15, 2018 7:38 AM
Mark Correct
Correct Answer
encryption enabled?
Like • Show 0 Likes0
Actions
Patrick Wong Jan 24, 2018 2:51 PM
Mark Correct
Correct Answer
Hi Ronald - I saw this problem after an upgrade as well. In my case, it was users who had cookies in their browser that was encrypted with the key in the previous RSA application. So when the users logged in to the new RSA application, the key wasn't present so it was unable to decrypt the cookie. After the user logs into the new application, a new cookie is encrypted and saved on their browser so they won't generate the message again. Hope this helps.
Like • Show 0 Likes0
Actions

adaptive authentication invalid padding

Outcomes

Related Content

Recommended Content