Control-M/Agent cannot connect to a RHEL9 Remote Host with signature algorithms other than SHA1 when using ssh-keys

Manage Support IDs

Use checkboxes to 'Remove support IDs/Users' or 'Allow to create Cases'
Support IDs for BMC Customer Support Site Guest User
Profiles Which Include    Back to All Support IDs
 

Knowledge Article

Control-M/Agent cannot connect to a RHEL9 Remote Host with signature algorithms other than SHA1 when using ssh-keys
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows all versions
In Control-M/Agent, when configuring a Remote Host connecting via SSH to a RedHat 9 or higher host, Run As user authentication via ssh-key does not work.

Authentication via Username/Password works correctly and is not affected.
Red Hat Enterprise Linux 9 OS default settings are not allowing signature algorithm using SHA1.
There is currently no support for using ssh-keys with signature algorithms other than SHA1.

Alternate Solution:
1) Login to the host that will be the Remote Host with the root user
2) Run the following command:
update-crypto-policies --set DEFAULT:SHA1
3) Reboot the host

Tracking Information:
CTM-9699 has been created for this issue and will be implemented in a future release.
"Password" authentication is not impacted by this issue.
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows all versions
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows all versions
Attachment(s):