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.

 Caution:

In SSH connections, the users must use the following as their username: gu=username@remoteusername, where username is the username used in the LDAP directory, SPS will use this username to determine their group memberships, and remoteusername is the username they will use on the remote server. For example, to access the example.com server as root, use:

gu=yourldapusername@root@example.com

For the username of SSH users, only valid UTF-8 strings are allowed.

 Caution:

In Telnet connections, usermapping policy works only if Extract username from the traffic is enabled.

For more information, see Extracting username from Telnet connections.

When configuring ICA connections, also consider the following:

 Caution:

If the clients are accessing a remote application or desktop that is shared for Anonymous users (that is, the Users properties of the application is set to Allow anonymous users in the Citrix Delivery Services Console), the actual remote session will be running under an Anonymous account name (for example, Anon001, Anon002, and so on), not under the username used to access the remote server. Therefore, you need to enable usermapping to the Anon* usernames.

To accomplish this, create a usermapping policy and set the Username on the server option to Anon*, and the Groups option to *, then use this usermapping policy in your ICA connections.

For more information on using usermapping policies, see Configuring usermapping policies.

NOTE: Starting from SPS version 3.2, usermapping is possible only when gateway authentication is used as well.

To configure usermapping

  1. Navigate to Policies > Usermapping Policies.

    Figure 326: 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 more information 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 more information 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, configure gateway authentication.

    For more information, see Configuring out-of-band gateway authentication.