When gateway authentication is required for a connection, the user must authenticate on One Identity Safeguard for Privileged Sessions (SPS) as well. This additional authentication can be performed:
Out-of-band, on the SPS web interface, for every protocol.
Inband, using the incoming connection, for the SSH, Telnet, and RDP protocols.
For details about the concepts of gateway authentication, see The gateway authentication process. You can use gateway authentication to authenticate the real person when the user is using a shared account to access the target server.
For SSH, Telnet, and RDP connections, gateway authentication can be performed also inband, without having to access the SPS web interface.
Gateway authentication can be used together with other advanced authentication and authorization techniques like four-eyes authorization, client- and server-side authentication, and so on.
If the username used within the protocol to access the remote server is different from the username used to perform gateway authentication (for example, because the user uses a shared account in the remote server, but a personal account for gateway authentication), usermapping must be configured for the connection. For details on usermapping, see Configuring usermapping policies.
To configure a credential store for gateway authentication, see Using credential stores for server-side authentication.
To configure gateway authentication
Navigate to the Connections page of the traffic (for example to SSH Control > Connections), and select the connection policy to modify.
Select the Require Gateway Authentication on the SPS Web Interface option. This is the option to configure gateway authentication via the web interface of SPS.
Figure 248: <Protocol name> Connections > Require Gateway Authentication on the SPS Web Interface — Configuring gateway authentication
To accept the gateway authentication only from the host that initiated the connection, select Require same IP.
This option has no effect if the clients are behind a device that performs network address translation (NAT). In such cases, use inband gateway authentication instead.
By default, any user can perform gateway authentication for the connections. To allow only members of a specific group authenticate the connections of this connection policy, select Groups, click and enter the name of the group whose members can authenticate the connections. This group must exist on the AAA > Group Management page. For details on creating and managing usergroups, see Managing user rights and usergroups. Repeat this step to add further groups if needed.
For SSH, RDP, Telnet and Citrix ICA connections, you may want to set a usermapping policy in the Usermapping policy field. For details on usermapping policies, see Configuring usermapping policies.
Click . After that, users accessing these connections must perform gateway authentication as described in Performing out-of-band gateway authentication on One Identity Safeguard for Privileged Sessions (SPS).
(Optional) To restrict the availability of selected channels of the connection based on the username used for gateway authentication, edit the channel policy used in the connection.
Navigate to the channel policy used in the connection (for example, SSH Control > Channel Policies).
Select Gateway Group, click and enter the name of the user group allowed to use this type of the channel. The user group must correspond to the username used for the gateway authentication. Repeat this step until all permitted groups are listed.
You may list local user lists as defined in Creating and editing user lists, or LDAP groups (for details on accessing LDAP servers from SPS, see Authenticating users to an LDAP server). Note the following behavior of SPS:
If you list multiple groups, members of any of the groups can access the channel.
When listing both a whitelist and blacklist in the Gateway Group section and a username appears on both lists, the user will be able to access the channel.
If a local user list and an LDAP group has the same name and the LDAP server is configured in the connection that uses this channel policy, both the members of the LDAP group and the members of the local user list can access the channel.
(Optional) If you want to provide a limited SPS web interface to your users that can be used only for gateway authentication and 4-eyes authorization, set up a dedicated user-only web login address. For details, see Configuring user and administrator login addresses.
(Optional) You can configure a message for users accessing SPS for out-of-band authentication. The message is displayed when they log in to SPS.
Navigate to Basic Settings > Management > Web gateway authentication.
Select Enable web gateway authentication banner.
Figure 249: Basic Settings > Management > Web gateway authentication — Configuring a banner
Enter the message in the Banner field. You can use the following text formatting options:
== Title == === Subtitle === This is plain text. [http://address.to/ Link text] # First numbered list item. # Second numbered list item. * First bulleted list item. * Second bulleted list item.
(Optional) If your users have sessions to several remote server, or access a server several times a day, performing the gateway authentication for every session can be a nuisance. To permit your users to authenticate on the SPS web interface once, and open sessions without repeating the gateway authentication, select Enable auto-assign and click . Note that the user must leave the browser window (or tab) of SPS open.
The following describes how to perform out-of-band gateway authentication on One Identity Safeguard for Privileged Sessions (SPS).
To perform out-of-band gateway authentication on SPS
Initiate a connection from a client. If gateway authentication is required for the connection, SPS will pause the connection.
For SSH and Telnet connections, when initiating the connection, you can use the following as your username: gu=gatewayusername@remoteusername, where gatewayusername is the username you will use to login to the SPS web interface (also called gateway user), and remoteusername is the username you will use on the remote server.
Open a browser, preferably on the same host you initiated the connection from, and navigate to the login page of SPS.
If the username used within the protocol is different from the username used to access the SPS web interface to perform gateway authentication, usermapping must be configured for the connection. For details on usermapping, see Configuring usermapping policies.
Log in to SPS, and select Gateway Authentication from the main menu. The list of connections waiting for gateway authentication will be displayed.
Figure 250: Gateway Authentication — Performing gateway authentication
Select the connection that you started, and click Assign.
Continue to authenticate on the server.
To authenticate another session, you must either:
repeat this procedure, or
if your SPS administrator has enabled the auto-assign feature, you do not have to repeat this procedure as long as the browser tab you authenticated on SPS is open.
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.
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.
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.