One Identity Safeguard for Privileged Sessions 6.0 LTS - Administration Guide

Configuring usermapping policies

For SSH, RDP, Telnet, and Citrix ICA connections, usermapping policies can be defined. A usermapping policy describes who can use a specific username to access the remote server: only members of the specified local or LDAP usergroups (for example, administrators) can use the specified username (for example, root) on the server.

gu=yourldapusername@root@example.com

When configuring ICA connections, also consider the following:

To configure usermapping

1. Navigate to Policies > Usermapping Policies.

   Figure 244: Policies > Usermapping Policies — Configuring usermapping policies

   

2. Click to create a new policy, and enter a name for the policy.

3. Click and enter the username that can be used to access the remote server (for example root) into the Username on the server field. SPS will use this username in the server-side connection. To permit any username on the server side, enter an asterisk (*).

4. Select Groups, click and specify who is permitted to use the remote username set in the Username on the server field.

   • If you have an LDAP Server set in the connection policy where you will use usermapping, enter the name of the local or LDAP usergroup (for example admins) whose members will be permitted to use the remote username. For details on LDAP authentication, see Authenticating users to an LDAP server.

     NOTE: The LDAP server configured in the connection policy is not necessarily the same as the LDAP server used to authenticate the users accessing the SPS web interface.

   • If you do not authenticate the connections to an LDAP server, enter the name of the userlist whose members will be permitted to use the remote username. For details on using userlists, see Creating and editing user lists.

   Repeat this step to add further groups if needed.

5. Repeat steps 3-4 to add further usernames if needed.

6. To permit other users, who are not explicitly listed in the Usermapping Policy access the remote servers, select the Allow other unmapped usernames option. Note that these users must use the same username on the SPS gateway and the remote server.

7. Click .

8. Navigate to the Connections page of the traffic (for example to SSH Control > Connections), and select the connection policy to modify.

9. Select the usermapping policy created in Step 2 from the Usermapping policy field.

10. Click .

    NOTE: For RDP connections, usermapping is possible only when gateway authentication is used as well. When configuring usermapping for RDP connections, proceed to Configuring out-of-band gateway authentication and configure gateway authentication.

Configuring gateway authentication

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.

Configuring out-of-band gateway authentication

To configure gateway authentication

1. Navigate to the Connections page of the traffic (for example to SSH Control > Connections), and select the connection policy to modify.

2. 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 245: <Protocol name> Connections > Require Gateway Authentication on the SPS Web Interface — Configuring gateway authentication

   

3. To accept the gateway authentication only from the host that initiated the connection, select Require same IP.

   NOTE: 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.

4. 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.

5. 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.

6. 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).

7. (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.

   1. Navigate to the channel policy used in the connection (for example, SSH Control > Channel Policies).

   2. 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.

        NOTE: 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.

   3. Click .

8. (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.

9. (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.

   1. Navigate to Basic Settings > Management > Web gateway authentication.

   2. Select Enable web gateway authentication banner.

      Figure 246: Basic Settings > Management > Web gateway authentication — Configuring a banner

      

   3. 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.

   4. Click .

10. (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.

Performing out-of-band gateway authentication on One Identity Safeguard for Privileged Sessions (SPS)

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

1. Initiate a connection from a client. If gateway authentication is required for the connection, SPS will pause the connection.

   NOTE: 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.

2. Open a browser, preferably on the same host you initiated the connection from, and navigate to the login page of SPS.

   Caution: 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.

3. Log in to SPS, and select Gateway Authentication from the main menu. The list of connections waiting for gateway authentication will be displayed.

   NOTE: If users accessing the SPS web interface are authenticated to and LDAP server, the users must successfully authenticate to the LDAP server set on the AAA > Settings page. No other SPS privilege is required to access this page.

   Figure 247: Gateway Authentication — Performing gateway authentication

   

4. Select the connection that you started, and click Assign.

5. Continue to authenticate on the server.

6. 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.