Chat now with support
Chat mit Support

One Identity Safeguard for Privileged Sessions 7.0.1 LTS - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS)
The philosophy of One Identity Safeguard for Privileged Sessions (SPS) Policies Credential Stores Plugin framework Indexing Supported protocols and client applications Modes of operation Connecting to a server through One Identity Safeguard for Privileged Sessions (SPS) Archive and backup concepts Maximizing the scope of auditing IPv6 in One Identity Safeguard for Privileged Sessions (SPS) SSH host keys Authenticating clients using public-key authentication in SSH The gateway authentication process Four-eyes authorization Network interfaces High Availability support in One Identity Safeguard for Privileged Sessions (SPS) Versions and releases of One Identity Safeguard for Privileged Sessions (SPS) Accessing and configuring One Identity Safeguard for Privileged Sessions (SPS)
Cloud deployment considerations 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 Using plugins Forwarding data to third-party systems Starling integration
User management and access control Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing One Identity 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 MSSQL-specific settings RDP-specific settings SSH-specific settings Using Sudo with SPS Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search interface Advanced authentication and authorization techniques Reports 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)
Network troubleshooting Gathering data about system problems Viewing logs on One Identity Safeguard for Privileged Sessions (SPS) Changing log verbosity level of One Identity Safeguard for Privileged Sessions (SPS) Collecting logs and system information for error reporting Collecting logs and system information of the boot process for error reporting Support hotfixes Status history and statistics Troubleshooting a One Identity Safeguard for Privileged Sessions (SPS) cluster Understanding One Identity Safeguard for Privileged Sessions (SPS) RAID status Restoring One Identity Safeguard for Privileged Sessions (SPS) configuration and data VNC is not working with TLS Configuring the IPMI from the BIOS after losing IPMI password Incomplete TSA response received Using UPN usernames in audited SSH connections
Using SPS with SPP Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help Configuring SPS to use an LDAP backend Glossary

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 an LDAP server, the users must successfully authenticate to the LDAP server set on the Users & Access Control > Settings page.

    Figure 325: 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.

Troubleshooting gateway authentication

If a user initiates a connection and then logs in to the One Identity Safeguard for Privileged Sessions (SPS) web interface, it might happen that his connection is not shown on the Gateway Authentication page. SPS checks the following points to determine if a pending connection is listed for a user:

 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.

  • The username used to access the SPS web interface is a member of a group listed in the Gateway authentication > Groups field of the connection policy.

  • If SPS knows from the protocol the username that will be used to access the SPS web interface to perform the gateway authentication, the connection is displayed only to this user.

    For SSH connections, SPS can determine the username if:

    • The client specifies the username for the web interface within the protocol using the gu=webusername@server-side-username@server format.

    • The client specifies the username within the protocol using an interactive prompt.

    • If the client does not use any of the above options, SPS uses the remote username. In this case, the username for the web interface must be the same as the remote username, otherwise the connection is not displayed.

  • If the Gateway authentication > Require same IP option is enabled, the pending connection is displayed only if the user accesses the SPS web interface from the same IP address as the client in the pending connection.

NOTE: The admin user sees every pending connection.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen