RSA authentication not working after upgrading to PAM 3.2

Article Id: 104129

Status: Published

Updated On: 06-07-2018 13:42

Products:

CA Privileged Access Manager - Cloakware Password Authority (PA) , PAM SAFENET LUNA HSM , CA Privileged Access Manager (PAM) , CA Privileged Access Manager (PAM)

Issue/Introduction:

One of the production PAM instances was upgraded to 3.2, after which RSA authentication stopped working. Support performed all the known steps for resolving the issue, but none worked.

Environment:

Release:
Component: CAPAMX

Resolution:

During a webex with RSA and PAM Support, the RSA Admin noticed that there was a certificate problem. Correcting the RSA server to use the same Root certificate as configured into PAM resolved the problem.