Unified Agent Installer - Remote Host Authentication (non-Windows)

The Remote Host Authentication (non-Microsoft Windows) panel specifies the communication protocol and the automation principal needed to authenticate to a remote non-Windows host on which an agent has not yet been installed. The automation principal provides the credential needed for authentication on the remote host.

Related agent installation object

The Unified Agent Installer uses the information you provide on this panel to create remote host authentications for non-Windows agentless devices. For detailed information about this type of object, see Specifying or modifying information for remote host authentication.

The Remote Host Authentication (non-Windows) panel only displays if you have chosen to install agents on a platform other than Windows.

Click Add g_V95_AddIcon.gifto open the Add Remote Host Authentication (non-Windows) window, or select an existing remote host authentication and click Edit g_V95_UpdateIcon.gif.

Note

If remote host authentications have been defined outside of the Unified Agent Installer, you cannot edit or delete them. To edit or delete one of these remote host authentications, use the Infrastructure Management window.

The Remote Host Authentication (non-Windows) window lets you provide the following information, which is used for authenticating to agentless devices. If you are installing on multiple platforms, typically you define at least one set of authentication information for each platform.

  • Protocol for accessing servers— Select one of the following:
    • SSH (Non-Windows) — Executes commands directly on an agentless host using the credentials defined in an automation principal that you specify on this panel.
    • SSH + SUDO (Non-Windows) — Executes commands directly on the agentless host using the credentials defined in an automation principal that you specify on this panel. The "sudo" command is attached as a prefix to all commands. If sudo requests a password, the password associated with the automation principal is used.
    • SSH + SU (Non-Windows) — Executes commands directly on the agentless host using the credentials defined in an automation principal that you specify on this panel. The automation principal credentials are used to access the agentless host. The credentials provided in a superuser automation principal are used to issue the "su" command to gain elevated privileges.
  • SSH port for communicating with servers — Specify the port number that is used by the SSH service running on the remote host. The default port is 22.
  • Select or create an automation principal — Select one of the following:
    • Select existing automation principal — Select this option then click Browseg_V95_BrowseIcon.gif to navigate to an existing automation principal.
    • Create new automation principal — Select this option and provide a user name and password for the automation principal. To use private key authentication, enter a private key file nsh path or use the Browse functionality to navigate to the private key file location. The user must have the relevant access permissions enabled for this file. 
  • Select or create a super user automation principal— Select one of the following. This option only becomes available when you select SSH + SU as the protocol for accessing servers.
    • Select existing automation principal — Select this option and then click Browse to navigate to an automation principal that should be used for the superuser.
    • Create new automation principal — Select this option. Then, provide a user name and password for the automation principal that should be used for the superuser.

Where to go from here

Unified-Agent-Installer-Remote-Host-Authentication-Windows

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*