PSMP Authentication Issue After Security Update – CyberArk PAM v14.4

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PSMP Authentication Issue After Security Update – CyberArk PAM v14.4

L1 Bithead

Dear Team,

I hope this email finds you well.

Kindly note that we are currently using CyberArk PAM Self-Hosted v14.4, with a PSMP server running Red Hat Enterprise Linux 9.7.

We recently performed the security update using the following command:

yum update --security

After completing the update, we attempted to connect to the target server through MobaXterm using the following PSMP connection format:

ssh vaultuser@serveruser@targetuser@PSMP_IP

However, after entering the command and providing the password, the system repeatedly prompts for the password again, and the authentication does not complete successfully.

We also checked the Vault server and observed the following error:

ITATS528E – Code -66

Could you please assist us in investigating this issue and advise whether it is related to the security update or any PSMP/Vault configuration?

Regards,

Omar Hweidi

1 accepted solution

Accepted Solutions

Dear @Donovan Demshock​ 

I hope this message finds you well.

 

Kindly note that after reviewing the logs on the PSMP server, we identified that the issue occurred after performing the following command:

yum update --security

Following the security update, the SSHD version was upgraded to 9.2, which appears to be related to the issue we experienced.

According to CyberArk's documentation, the SSHD version supported by the PSM for SSH machine is between 7.8 and 9.2 for the relevant supported features.

To resolve the issue without reverting the complete security update or losing the other security updates and features, we need to perform the following steps:

 

1. Downgrade OpenSSH to the required version

Run the following commands:

V=8.7p1-48.el9_7

tar czf /root/ssh_pam_backup_$(date +%F_%H%M).tgz /etc/ssh /etc/pam.d

dnf downgrade -y openssh-$V openssh-server-$V openssh-clients-$V

md5sum /etc/ssh/sshd_config

# The expected MD5 checksum should be:

# 7d2024dd5ce68b48dd8226f7ee68dbb2

sshd -t && systemctl restart sshd

 

2. Lock the OpenSSH version on both servers

This will prevent future updates from upgrading OpenSSH again and potentially reintroducing the PSMP issue.

dnf install -y python3-dnf-plugin-versionlock

dnf versionlock add openssh-$V openssh-server-$V openssh-clients-$V

dnf versionlock list

 

3. Restart services and verify PSMP

After completing the above steps, run:

systemctl daemon-reload

systemctl restart psmpsrv

systemctl restart sshd

 

After completing these steps, we can retest the PSMP Linux connections to confirm that the issue has been resolved.

 

Regards,

Omar Hweidi

View solution in original post

2 REPLIES 2

L4 Transporter

Hello,

You will have to check logs on the PSMP to be certain, but I believe the update you applied to the Operating System likely changed something related to OpenSSH and caused the issue.

var/opt/CARKpsmp/logs is the default location for PSMP logs.

 

Have you restarted PSMP services?

If restarting services doesn't help, a repair may have you up and running again very quickly, but you should review logs first.

Dear @Donovan Demshock​ 

I hope this message finds you well.

 

Kindly note that after reviewing the logs on the PSMP server, we identified that the issue occurred after performing the following command:

yum update --security

Following the security update, the SSHD version was upgraded to 9.2, which appears to be related to the issue we experienced.

According to CyberArk's documentation, the SSHD version supported by the PSM for SSH machine is between 7.8 and 9.2 for the relevant supported features.

To resolve the issue without reverting the complete security update or losing the other security updates and features, we need to perform the following steps:

 

1. Downgrade OpenSSH to the required version

Run the following commands:

V=8.7p1-48.el9_7

tar czf /root/ssh_pam_backup_$(date +%F_%H%M).tgz /etc/ssh /etc/pam.d

dnf downgrade -y openssh-$V openssh-server-$V openssh-clients-$V

md5sum /etc/ssh/sshd_config

# The expected MD5 checksum should be:

# 7d2024dd5ce68b48dd8226f7ee68dbb2

sshd -t && systemctl restart sshd

 

2. Lock the OpenSSH version on both servers

This will prevent future updates from upgrading OpenSSH again and potentially reintroducing the PSMP issue.

dnf install -y python3-dnf-plugin-versionlock

dnf versionlock add openssh-$V openssh-server-$V openssh-clients-$V

dnf versionlock list

 

3. Restart services and verify PSMP

After completing the above steps, run:

systemctl daemon-reload

systemctl restart psmpsrv

systemctl restart sshd

 

After completing these steps, we can retest the PSMP Linux connections to confirm that the issue has been resolved.

 

Regards,

Omar Hweidi

  • 1 accepted solution
  • 71 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!