Chatta subito con l'assistenza
Chat con il supporto

One Identity Safeguard for Privileged Sessions 6.0.1 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS) The Welcome Wizard and the first login Basic settings
Supported web browsers and operating systems The structure of the web interface Network settings Configuring date and time System logging, SNMP and e-mail alerts Configuring system monitoring on SPS Data and configuration backups Archiving and cleanup Forwarding data to third-party systems Joining to One Identity Starling
User management and access control Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing Safeguard for Privileged Sessions (SPS) clusters Managing a high availability One Identity Safeguard for Privileged Sessions (SPS) cluster Upgrading One Identity Safeguard for Privileged Sessions (SPS) Managing the One Identity Safeguard for Privileged Sessions (SPS) license Accessing the One Identity Safeguard for Privileged Sessions (SPS) console Sealed mode Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS) Managing the certificates used on One Identity Safeguard for Privileged Sessions (SPS)
General connection settings HTTP-specific settings ICA-specific settings RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search interface Searching session data on a central node in a cluster Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) RPC API The One Identity Safeguard for Privileged Sessions (SPS) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS) Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help LDAP user and group resolution in SPS Appendix: Deprecated features

Configuring out-of-band gateway authentication

 Caution:

  • The admin user is a special One Identity Safeguard for Privileged Sessions (SPS) user and not a member of any user groups, nor can it belong to any group. Since usermapping policies are based on user groups, performing gateway authentication with the admin user is likely to result in usermapping errors.

  • When using SSL-encrypted RDP connections, or connections that use the Credential Security Service Provider (CredSSP) authentication method, some Microsoft RDP clients restart the connection during the authentication process. This would require the user to perform gateway authentication on the SPS web interface twice. To avoid this situation, SPS temporarily caches the successful gateway authentication results if the client terminates the connection at a certain step while establishing the connection. The cache is used to automatically authenticate the restarted connection without user interaction.

    In this case, the restarted connection coming from the same source IP and targeting the same destination IP:port pair will be authenticated from the cache. The cache is deleted after three minutes, or when a connection is authenticated from the cache.

    However, caching the authentication results has the following side-effect: if a different connection targets the same destination IP:port pair from seemingly the same source IP address within the brief period when SPS expects the original connection to be re-established, the new connection can access the target server without having to authenticate on the SPS gateway. Normally, this can occur only if the clients are behind a NAT.

  • If the clients are behind a device that performs network address translation (NAT), it will seem to SPS as if every connection was initiated from the same IP address. Therefore, in such cases using out-of-band gateway authentication is not recommended for security reasons, especially for RDP connections. If possible, use inband gateway authentication instead.

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 247: <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 Commit. 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 Commit.

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

  1. (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 248: 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 Commit.

  2. (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 Commit. 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 249: 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.

Performing inband gateway authentication in SSH and Telnet connections

The following describes how to perform inband gateway authentication in SSH and Telnet connections.

To perform inband gateway authentication in SSH and Telnet connections

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

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

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

    		 Caution:

    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.

    		 NOTE:

    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.

Performing inband gateway authentication in RDP connections

The following describes how to perform inband gateway authentication in RDP connections.

To perform inband gateway authentication in RDP connections

  1. Initiate a connection from a client.

  2. The graphical login window is displayed.

    • If the Advanced > Remote Desktop Gateway > Logon Settings > Use my Remote Desktop Gateway credentials for the remote computer option of your Remote Desktop application is enabled, login to the remote server using your usual credentials. One Identity Safeguard for Privileged Sessions (SPS) will use these credentials for the gateway authentication on the Domain Controller as well.

    • If the Advanced > Remote Desktop Gateway > Logon Settings > Use my Remote Desktop Gateway credentials for the remote computer option of your Remote Desktop application is disabled, first you have to authenticate on the SPS gateway. Enter your username and password for the Domain Controller.

      If the first authentication is successful, a second login window is displayed. Enter your username and password for the remote server you are trying to access.

    • If SPS is configured to use a Credential Store to login to the target server, enter the following:

      • In the Username field, enter the domain name, the -AUTO suffix, and your username. For example, EXAMPLEDOMAIN-AUTO\Administrator.

        		 NOTE:

        The -AUTO suffix is the default value of the RDP Control > Settings > Autologon domain suffix option of One Identity Safeguard for Privileged Sessions (SPS). If your SPS administrator has changed this option, use the appropriate suffix instead of -AUTO.

      • Enter your username (only the username, without the domain, for example, Administrator) into the Password field.

  3. If the authentication is successful, the desktop of the remote server is displayed.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione