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
Unable to SSH SA Appliances during the 10.6.2 upgrade and received update error in host page 5Number of Views RACF-SSH based connector fails with Unable to Negotiate Key Exchange error in RSA Governance & Lifecycle 17Number of Views Unable to authenticate with Authentication Agent for PAM for SSH due to SELinux 198Number of Views Certificate verification failed and ConfigResponse is not valid for RSA Authentication Agent API 8.5 and later 322Number of Views Web Server certificate verification failed with RSA Authentication Agent 8.0 for Web for Apache 76Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…