立即与支持人员聊天
与支持团队交流

Safeguard for Privileged Sessions On Demand Hosted - 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 and cleanup 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 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.

Configuring four-eyes authorization

When four-eyes authorization is required for a connection, a user (called authorizer) must authorize the connection on One Identity Safeguard for Privileged Sessions (SPS) as well. This authorization is in addition to any authentication or group membership requirements needed for the user to access the remote server. For details about the concepts of four-eyes authorization, see Four-eyes authorization.

Topics:

Configuring four-eyes authorization

The following describes how to configure four-eyes authorization.

To require four-eyes authorization for a connection

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

  2. Figure 326: <Protocol name> Control > Connections > Access Control — Configuring four-eyes authorization

    Navigate to Access Control and click .

  3. Enter the name of the usergroup whose members are permitted to authorize the sessions of the connection policy into the Authorizer Group field. This group must exist on the Users & Access Control > Local User Groups page. For details on creating and managing usergroups, see Managing user rights and usergroups.

    		 Caution:

    Usernames, the names of user lists, and the names of usergroups are case sensitive.

  4. By default, the authorizer can authorize any session of the connection policy.

    If the authorizer is permitted to authorize only the sessions of a certain usergroup, select Client user is > Member of, and enter the name of the userlist whose sessions the authorizer can authorize. If you use four-eyes authorization without gateway authentication, you can specify an LDAP group instead of a userlist.

    		 Caution:

    Usernames, the names of user lists, and the names of usergroups are case sensitive.

    		 Caution:

    When using both gateway authentication and four-eyes authorization in a Connection Policy, specify the usergroup of the gateway username. The specified group must be a local or LDAP group.

  5. Set the permissions of the usergroup set in the Authorizer Group field.

    • If the Authorizer group can authorize (that is, enable) and audit (that is, monitor in real-time and download the audit trails) the sessions, select Permission > Follow&Authorize.

    • If the Authorizer group can only authorize (that is, enable) the sessions, select Permission > Authorize.

      NOTE: This option is not valid for HTTP connections.

    • If the Authorizer group can only audit (that is, monitor in real-time and download the audit trails) the sessions, select Permission > Follow.

    NOTE: If the Client user is > Member of field is set, the auditor can only monitor the sessions of the specified usergroup. However, if Client user is > Member of field is set, the Auditor cannot access the Search page. To avoid this problem, add another Access Control rule for the Authorizer Group without setting the Client user isfield.

    The admin user of One Identity Safeguard for Privileged Sessions (SPS) can audit and authorize every connection.

  6. To ensure that the client and the authorizer use different IP addresses and thus prevent self-authorization, enable Require different IP. If this is enabled, and the client and the authorizer do not have different IP addresses, it disables all actions for the connection and the four-eyes authorization, until they have different IP addresses.

  7. To ensure that the client and the authorizer use different usernames and thus prevent self-authorization, enable Require different Username. If this is enabled, and the client and the authorizer do not have different usernames, it disables all actions for the connection and the four-eyes authorization, until they have different usernames.

  8. Repeat steps 2-6 to add other authorizers or usergroups if needed.

  9. Click .

  10. Navigate to the Channel Policies page of the traffic (for example, to SSH Control > Channel Policies), and select the channel policy used in the connection.

    Figure 327: <Protocol name> Control > Channel Policies — Configuring four-eyes authorization in the channel policy

  11. Enable the Four-eyes option for the channels which should be accessed only using four-eyes authorization.

    NOTE: If a connection uses secondary channels that require four-eyes authorization — for example, a Remote Desktop connection allows a Drawing channel but requires four-eyes authorization for a Disk redirection channel — the connection is locked until the authorizer accepts the channel on the Four-Eyes page of SPS, or the four-eyes request times out. During this time, the client application can become nonresponsive, for example, display the graphical desktop but not react to mouse clicks.

    NOTE: In Citrix ICA connections, four-eyes authorization is required before the user logs in to the destination server. To request four-eyes authorization only after the log in, when the server-side username is already known, select the Perform 4 eyes after user login option.

  12. Click . After that, users accessing connections using the modified channel policy must be authorized as described in Performing four-eyes authorization on One Identity Safeguard for Privileged Sessions (SPS).

  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.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级