SSH Credential authentication fails with error "no suitable key exchange algorithm was agreed"Issue Customer ran a discovery of a Linux server using configured SSH Credentials. Discovery fails and upon enabling mid.ssh.debug MID Server debug parameter, the following error message is logged in the MID Server agent.log log: SSH authentication or connection failure --> No suitable key exchange algorithm could be agreed.ReleaseAllCauseDuring SSH authentication, the server provides its public host key, which the client can use to check whether this was the intended host. During this phase, the server and client negotiate a session key using a version of the Diffie-Hellman algorithm. The key exchange method specifies how one-time session keys are generated for encryption and for authentication, and how the server authentication is done. As per the SSH specification RFC 4253 diffie-hellman-group1-sha1 is a required exchange method, therefore the server must accept it. ResolutionPlease refer to the article below: Enabling SNC SSH to support newer and more secure cipher algorthms for the Discovery process (i.e AES 256 encryption)