Automation can create less secure keys based on user generated input that may not be compatible with endpoints like SFTP Hosts for MOVEit Transfer. Creating a key in MOVEit Automation that uses an old Ed25519 key may be an option, but assigning it to the SSH/SFTP Host by using the Client Key button, the admin may not see the new key. Connecting with MOVEit Transfer hosts using an SSH/SFTP Host connection may show this type of error. 

There could be several causes to these types of credentials errors: 

Cause 1: Authentication can fail if the password or SSH client key configured in the host is incorrect, or if the user requires a different authentication method than what was configured in the host.

Cause 2: An old SSH Client Keys need to be updated to be compatible with more recent algorithms. Most often, this has been seen with Ed25519 keys. This cause presented often after upgrading to 2024.1 or 2025.0 due to new security requirements. 

Cause 3: The error message will show which authentication methods are allowed for the user. In the example error message above, it is showing that the user is allowed to authenticate with the publickey method, which is an SSH client key. If an SFTP server has a user set up such that it must authenticate with an SSH client key and not a password, then authenticating with only a password will not be successful.

In the Username text box, the username is spelled as myUsernamep (lowercase p).
The actual username is myUsernameP (uppercase P).

If unsure what authentication methods are required for the user, confirm with the team that manages the SSH/SFTP server. Update the host in MOVEit Automation accordingly.

If the issue is that the user requires authenticating with SSH client key, generating an SSH key and applying it to the host user should be successful, although it may be necessary to work with the host server admins to accept the key and/or to send them a copy of the public key.

1. Create a new SSH Client Key with ECDSA or RSA algorithms. 
2. Go to the affected SSH/SFTP Host Profile
3. Click the Client Key button
4. Select the new ECDSA or RSA key. 
5. Save the changes
6. Send the Public portion of the Client Key to the SSH/SFTP Host administrator. They will need to register the Public portion of the client key to accept the
7. Return to the SSH/SFTP Host profile to Test the connection. 

Ensure that the username placed in the host definition uses the correct casing.

If the host server admins update the user to allow for password authentication and they set an appropriate password, then logging in that way will also work.

References to Other Documentation:

MOVEit Automation Web Admin Help > Hosts ? Supported Host Types > SSH/SFTP Field Descriptions

https://docs.progress.com/bundle/moveit-automation-web-admin-help-2025/page/SSHSFTP-Host-Field-Descriptions.html