- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
09-22-2025 03:50 AM
We are currently migrating from an older PSMP server (version 12.2) to two newly deployed PSMP servers, which will be placed behind a load balancer and accessed via a common FQDN (e.g., psmp.domain.com).
In the legacy setup, all users have been connecting through the existing PSMP server for a long time, and their SSH clients have already cached the host key of this server.
Our plan is to decommission the old PSMP and replace it with two new PSMP servers. To avoid SSH host key mismatch errors for end users, we are considering copying the existing host key files (
/etc/ssh/ssh_host_*
) from the old PSMP server and applying them to the new PSMP servers before putting them behind the load balancer.
Question:
09-22-2025 07:00 PM
Hi @Rashid Afandiyev
Yes, copying the host key files from the old PSMP server to the new ones is a supported and recommended approach for this specific migration scenario.
https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/configuring-the-verification-of-a-servers-host-key.htm
https://community.cyberark.com/s/question/0D52J00009iEHMASA4/how-to-resolve-warning-potential-security-breach-
When users connect to a server for the first time, their SSH client saves the server's public key to a file called
known_hosts.This key is then used to verify the server's identity on subsequent connections. In your environment, all connections will be routed through the same FQDN psmp.domain.com but they will connect either of the two new servers. If these servers have different host keys, the client will detect a mismatch, and trigger a security warning. Hence by ensuring all PSMP servers including the old one and the new ones share the same host key, you ensure a consistent key and eliminating the host key mismatch error.
The risks are reusing a host key across multiple servers means if one of those PSMP servers is compromised and its private key is stolen, an attacker can impersonate all servers using that key. If you plan to rotate these keys, the risk can be reduced.
As a best practice hhen copying the key files /etc/ssh/ssh_host_* please ensure you replicate the exact permissions.
Hope it helps !
09-22-2025 07:00 PM
Hi @Rashid Afandiyev
Yes, copying the host key files from the old PSMP server to the new ones is a supported and recommended approach for this specific migration scenario.
https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/configuring-the-verification-of-a-servers-host-key.htm
https://community.cyberark.com/s/question/0D52J00009iEHMASA4/how-to-resolve-warning-potential-security-breach-
When users connect to a server for the first time, their SSH client saves the server's public key to a file called
known_hosts.This key is then used to verify the server's identity on subsequent connections. In your environment, all connections will be routed through the same FQDN psmp.domain.com but they will connect either of the two new servers. If these servers have different host keys, the client will detect a mismatch, and trigger a security warning. Hence by ensuring all PSMP servers including the old one and the new ones share the same host key, you ensure a consistent key and eliminating the host key mismatch error.
The risks are reusing a host key across multiple servers means if one of those PSMP servers is compromised and its private key is stolen, an attacker can impersonate all servers using that key. If you plan to rotate these keys, the risk can be reduced.
As a best practice hhen copying the key files /etc/ssh/ssh_host_* please ensure you replicate the exact permissions.
Hope it helps !
09-24-2025 04:39 AM
Thanks it works normally
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!

