One Identity Safeguard for Privileged Sessions 8.0 LTS

When using One Identity Safeguard for Privileged Sessions (SPS) in non-transparent mode, the administrators must address SPS to access the protected servers. If an administrator has access to more than one protected server, SPS must be able to determine which server the administrator wants to access. For each protected server, the administrators must address either different ports of the configured interface, or different alias IP addresses.

Detailed information about this topic

Organizing connections based on port numbers

Organizing connections based on alias IP addresses

Organizing connections based on port numbers

To allow the administrators to access protected servers by connecting to the IP address of One Identity Safeguard for Privileged Sessions (SPS), and use the port number to select which server they want to access. Organizing connections based on port numbers is advantageous if SPS has a public IP address and the protected servers must be administered from the Internet.

NOTE: Do not use the listening addresses configured for web login. For more details, see Configuring user and administrator login addresses.

For details on configuring alias IP addresses, see Managing logical interfaces.

To organize connections based on port numbers

Navigate to the Connections tab of the Traffic Controls > SSH menu.
Add a new connection. Enter the IP address of the administrators into the From fields, and the IP address and port number of the server into the Target field.
Enter the IP address of the logical interface of SPS into the To field, and enter a port number into the Port field.
Repeat Steps 2-3 for every protected server, but every time use a different port number in Step 3.
Click Commit.

Organizing connections based on alias IP addresses

To allow the administrators to access protected servers by connecting to an alias IP address of One Identity Safeguard for Privileged Sessions (SPS). The alias IP address determines which server they will access. Organizing connections based on alias IP addresses is advantageous if SPS is connected to a private network and many private IP addresses are available.

NOTE: Do not use the listening addresses configured for web login. For more details, see Configuring user and administrator login addresses.

To organize connections based on alias IP addresses

Navigate to Basic Settings > Network.
Set up a logical interface: click and configure a new logical interface. Add alias IP addresses for every protected server. (Use a different IP address for each.)

For more information on configuring logical interfaces and alias IP addresses, see Managing logical interfaces.
Navigate to Traffic Controls > SSH > Connections.
Add a new connection. Enter the IP address of the administrators into the From fields, and the IP address and port number of the target server into the Target field.
Enter an alias IP address of the configured logical interface of SPS into the To field.
Repeat Steps 4-5 for every protected server, but every time use a different alias IP address in Step 5.
Click Commit.

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
If you do not specify the username or the address in nontransparent SSH and Telnet connections, One Identity Safeguard for Privileged Sessions (SPS) displays an interactive prompt where you can enter the username and the server address.