The following describes how to perform inband gateway authentication in SSH and Telnet connections.
To perform inband gateway authentication in SSH and Telnet connections
-
Initiate a connection from a client. If gateway authentication is required for the connection, One Identity Safeguard for Privileged Sessions (SPS) will pause the connection.
-
SPS requests the username used for gateway authentication. Enter your gateway username into the Gateway username prompt. If password authentication is used, provide the password for the gateway user as well.
-
The login prompt for the remote server is displayed. Enter your username used on the remote server into the Username prompt. If password authentication is used, provide the password for the username as well.
|
|
Caution:
If the username used within the protocol to access the remote server is different from the username used to perform gateway authentication, usermapping must be configured for the connection. For details on usermapping, see Configuring usermapping policies. |
NOTE: When initiating the connection, you can use the following as your username: gu=gatewayusername@remoteusername, where gatewayusername is the username you will use to authenticate on SPS and remoteusername is the username you will use on the remote server. That way you do not have to provide the usernames in the prompt, only the passwords if password authentication is used.
If SPS is configured to require client-side authentication, the gatewayusername user must authenticate on the client side.
The following describes how to perform inband gateway authentication in RDP connections.
To perform inband gateway authentication in RDP connections
-
Initiate a connection from a client.
-
The graphical login window is displayed.
-
If the Advanced > Remote Desktop Gateway > Logon Settings > Use my Remote Desktop Gateway credentials for the remote computer option of your Remote Desktop application is enabled, login to the remote server using your usual credentials. One Identity Safeguard for Privileged Sessions (SPS) will use these credentials for the gateway authentication on the Domain Controller as well.
-
If the Advanced > Remote Desktop Gateway > Logon Settings > Use my Remote Desktop Gateway credentials for the remote computer option of your Remote Desktop application is disabled, first you have to authenticate on the SPS gateway. Enter your username and password for the Domain Controller.
If the first authentication is successful, a second login window is displayed. Enter your username and password for the remote server you are trying to access.
-
If SPS is configured to use a Credential Store to login to the target server, enter the following:
-
In the Username field, enter the domain name, the -AUTO suffix, and your username. For example, EXAMPLEDOMAIN-AUTO\Administrator.
NOTE: The -AUTO suffix is the default value of the Traffic Controls > RDP > Settings > Autologon domain suffix option of One Identity Safeguard for Privileged Sessions (SPS). If your SPS administrator has changed this option, use the appropriate suffix instead of -AUTO.
-
Enter your username (only the username, without the domain, for example, Administrator) into the Password field.
-
If the authentication is successful, the desktop of the remote server is displayed.
If a user initiates a connection and then logs in to the One Identity Safeguard for Privileged Sessions (SPS) web interface, it might happen that his connection is not shown on the Pending Connections > Gateway Authentication page. SPS checks the following points to determine if a pending connection is listed for a user:
|
|
Caution:
The admin user is a special One Identity Safeguard for Privileged Sessions (SPS) user and not a member of any user groups, nor can it belong to any group. Since usermapping policies are based on user groups, performing gateway authentication with the admin user is likely to result in usermapping errors. |
-
The username used to access the SPS web interface is a member of a group listed in the Gateway authentication > Groups field of the connection policy.
-
If SPS knows from the protocol the username that will be used to access the SPS web interface to perform the gateway authentication, the connection is displayed only to this user.
For SSH connections, SPS can determine the username if:
-
The client specifies the username for the web interface within the protocol using the gu=webusername@server-side-username@server format.
-
The client specifies the username within the protocol using an interactive prompt.
-
If the client does not use any of the above options, SPS uses the remote username. In this case, the username for the web interface must be the same as the remote username, otherwise the connection is not displayed.
-
If the Gateway authentication > Require same IP option is enabled, the pending connection is displayed only if the user accesses the SPS web interface from the same IP address as the client in the pending connection.
NOTE: The admin user sees every pending connection.
When four-eyes authorization is required for a connection, a user (called authorizer) must authorize the connection on One Identity Safeguard for Privileged Sessions (SPS) as well. This authorization is in addition to any authentication or group membership requirements needed for the user to access the remote server. For details about the concepts of four-eyes authorization, see Four-eyes authorization.
Detailed information about this topic
