One Identity Safeguard for Privileged Sessions 6.0.4 - Administration Guide

Using inband destination selection in SSH connections

The following sections provide examples for using inband destination selection to establish an SSH connection, including scenarios where nonstandard ports or gateway authentication is used.

Since some client applications do not permit the @ and : characters in the username, alternative characters can be used as well:

• To separate the username and the target server, use the @ or % characters, for example: username%targetserver@scb_address

• To separate the target server and the port number, use the :, +, or / characters, for example: username%targetserver+port@scb_address

For detailed instructions on configuring inband authentication, see Configuring inband destination selection.

Using inband destination selection with PuTTY

To establish an SSH connection through One Identity Safeguard for Privileged Sessions (SPS) with PuTTY, follow one of the methods:

Common method

To establish the SSH-connection using the most common method, enter the username, the target server's hostname (or IP address), and the hostname (or IP address) of SPS using the <username>@<server>@<scb> format in PuTTY.

Figure 273: Configuring SSH inband destination in PuTTY

Alternative method

To establish the SSH-connection using a different method,

1. Enter only the hostname (or IP address, depending on your configuration) of SPS in PuTTY.

2. At the login prompt, provide the username on the target server, and the target server's hostname (or IP address) using the <username>@<server> format.

Using inband destination selection with OpenSSH

To establish an SSH connection through One Identity Safeguard for Privileged Sessions (SPS), follow these steps:

1. Enter the following command:

   # ssh <username>@<server>@<scb>

   ...where <username> is the username, <server> is the target server's hostname (or IP address), and <scb> is the hostname (or IP address) of SPS

   Example

   Assuming the following values:

   • The username is training1

   • The target server is linux.training.example

   • The SPS server is scb

   You can enter the following command:

   # ssh training1@linux.training.example@scb

2. Alternative approach:

   1. Enter only the hostname (or IP address, depending on your configuration) of SPS:

      # ssh <scb>

   2. At the login prompt, provide the username on the target server, and the target server's hostname (or IP address) using the <username>@<server> format

Using inband selection and nonstandard ports with PuTTY

The following steps provide instructions for establishing SSH connections with servers that are listening on a non-standard port (the Inband destination selection > Targets > Port option is not 22), and the port number targeted by the clients is also a non-standard port (the To > Port option of the Connection Policy).

1. Enter the following in PuTTY:

   1. In the Host Name field, enter the username on the target server, the target server's hostname (or IP address) and port number, and the hostname (or IP address) of One Identity Safeguard for Privileged Sessions (SPS) in the <username>@<server>:<port>@<scb> format

   2. In the Port field, enter the port number of the SPS server

   Example

   Assuming the following values:

   • The username is training1

   • The target server is 192.168.60.100

   • The target server is listening on port 2121

   • The SPS server is scb

   • The SPS server is listening on port 4444

   You can enter the following destination hostname in PuTTY:

   training1@192.168.60.100:2121@scb

   Also change the destination port to the SPS server's port number:

   4444

   Figure 274: Configuring SSH inband destination for nonstandard ports in PuTTY

   

2. Alternative approach:

   1. Enter only the hostname (or IP address, depending on your configuration) and port number of SPS in PuTTY.

   2. At the login prompt, provide the username on the target server, and the target server's hostname (or IP address) and port number using the <username>@<server>:<port> format.