search cancel

Client login issues using Radius Authentication after upgrade to 4.0.1


Article ID: 238227


Updated On:


CA Privileged Access Manager (PAM)


We are upgrading our test environment from 3.4.2 to 4.0.1.  After restarting the cluster, we connected via client.  The client takes updates and then asks for a client restart, as expected.  
At this point, a login attempt appears to have a greater than 50% chance of only giving us a blank screen. When that doesn't hang, we find that the form prompting us for the Radius passcode is not rendering well, but shows in plain text and left-aligned instead of centered.


One problem was with stale CAPAMClient.exe processes running in the background that had been started prior to the upgrade.

The form rendering problem was due to a problem in the PAM client code related to the updated PAM client browser (JxBrowser) version included in the 4.0.1 client. This problem also could lead to a client hang in some cases.


Release : 4.0.1



If you have a problem with the PAM Client hanging during or even prior to authentication, use Task Manager to identify any running CAPAMClient.exe process and kill them before starting the PAM client new.

The problem that existed w/o stale processes involved is resolved in PAM 4.0.2, see the following item on page Resolved Issues in 4.0.2:

DE528189 33019179 Problems with Radius passcode prompt after upgrading from 3.4.2 to 4.0.1.


If you have this problem with 4.0.1 and cannot upgrade to 4.0.2 or a newer release in a timely fashion, please open a case with PAM Support and request a hotfix on top of 4.0.1.