RSA Product/Service Type: Identity Router
The occurrence of the "REMOTE HOST IDENTIFICATION HAS CHANGED" issue is caused by a change in the key used by the IDR. Specifically, the sshd initially selects the ecdsa-sha2-nistp25 key instead of the configured ssh-rsa key. Consequently, when a user attempts to establish an SSH connection, the ecdsa key is added to the known_hosts file. However, if the sshd is restarted or IDR is upgraded, resulting in a service reboot, the sshd will then utilize the configured ssh-rsa key. Consequently, when a user tries to SSH into the server, the server will present a different key than the one stored in the known_hosts file, leading to a failure in host authentication.
To resolve this issue, the user is prompted to run the sshkey command.
It is worth noting that this change in key does not have any adverse effects and only occurs once during the lifetime of IDR when transitioning from the ecdsa-sha2 key to the ssh-rsa key to align with the configuration file.
The fix is to run the below command:
ssh-keygen -R 127.0.0.1 -f /home/idradmin/.ssh/known_hosts
Related Articles
How to validate an installation or restored database in RSA Identity Governance & Lifecycle 56Number of Views RSA Federated Identity Manager "failed to validate signature value" error 40Number of Views intermittant FIM "error failed to validate signature value" 31Number of Views Certificate verification failed and ConfigResponse is not valid for RSA Authentication Agent API 8.5 and later 322Number of Views Unable to authenticate with Authentication Agent for PAM for SSH due to SELinux 202Number of Views