Okta Advanced Server Access or Privileged Access Fails With a No Supported Methods Remain Error

Target server configuration issues or disabled server user management cause an Okta Advanced Server Access or Okta Privileged Access connection failure. Modifying the secure shell daemon configuration file or enabling server user management resolves this issue. An administrator experiences a connection failure when attempting to access a target server using the ScaleFT client. Okta generates the following error:

error: ssh: Handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Advanced Server Access (ASA)
• Okta Privileged Access (OPA)
• ScaleFT Client

The target server rejects secure shell (SSH) connections on port 22 or the configured SSH port. This occurs if the sshd_config file contains specific Allow directives that interfere with the Okta Advanced Server Access or Okta Privileged Access authentication flow, or if an administrator disables the Server User Management setting in the Okta Advanced Server Access project, preventing access management.

How is the Secure Shell Daemon configuration modified for Okta Advanced Server Access and Okta Privileged Access?

Modify the secure shell daemon configuration file to remove restrictive flags and reorder the trusted user keys by following these steps.

1. Log in to the Linux server outside of the ScaleFT client and navigate to the /etc/ssh/ directory.
2. Open the sshd_config file using a text editor.
3. Check for Allow flags that limit specific users or groups from accessing the server, such as AllowUsers or AllowGroups, and modify them as needed.
4. Move the TrustedUserCAKeys line above the Match group line in the /etc/ssh/sshd_config file.
5. Restart the sshd service.

How is the Server User Management setting enabled for Okta Advanced Server Access?

Verify the project settings and enable the server user management option using the Okta Advanced Server Access application programming interface (API) by following these steps.

1. Ensure that the project settings include the Server User Management option.
   
2. If the project lacks this option, enable it using the Update Project API call.