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

One Identity Safeguard for Privileged Sessions 7.5 - 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 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 Cleaning up audit data Using plugins Forwarding data to third-party systems Starling integration
User management and access control
Login settings Managing One Identity Safeguard for Privileged Sessions (SPS) users locally Setting password policies for local users Managing local user groups Managing One Identity Safeguard for Privileged Sessions (SPS) users from an LDAP database Authenticating users to a RADIUS server Authenticating users with X.509 certificates Authenticating users with SAML2 Managing user rights and usergroups Creating rules for restricting access to search audit data Displaying the privileges of users and user groups Listing and searching configuration changes
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

Configuring SPS for Sessions-initiated workflow

To configure SPS to use the linked SPP in Sessions-initiated (SPS-initiated) workflows, complete the following steps. For details on the workflow, see Using SPS with SPP.

Prerequisites

  • Minimum versions:

    • SPP version 2.8

    • SPS version 6.2 and newer, including 6.0.2 and newer versions of the 6.0.x branch, but excluding 6.1.x

  • You must have built an SPS cluster by promoting an SPS node to the role of Central Management node, even if it is a single node. For more information, see Creating a cluster.

CAUTION: When linking your One Identity Safeguard for Privileged Sessions (SPS) deployment to your One Identity Safeguard for Privileged Passwords (SPP) deployment, ensure that the SPS and SPP versions match exactly, and you keep the versions synchronized during an upgrade. For example, you can only link SPS version 6.6 to SPP version 6.6, and if you upgrade SPS to version 6.7, you must also upgrade SPP to 6.7.

Make sure that you do not mix Long Term Supported (LTS) and feature releases. For example, do not link an SPS version 6.0 to an SPP version 6.1.

Limitations

  • Only SSH and RDP sessions are supported.

  • Users must perform gateway authentication on SPS with the same username they have Entitlements for in SPP.

    • For SSH sessions, the gateway authentication can use a Local User Database, an LDAP server, or an Active Directory server as authentication backend.

      Note that SPP does not support every type of LDAP and Active Directory settings that SPS does. Verify that you can configure both appliances to access and retrieve data from the LDAP or Active Directory server.

    • For RDP sessions, SPS must be configured to act as a Remote Desktop Gateway. For details, see Using One Identity Safeguard for Privileged Sessions (SPS) as a Remote Desktop Gateway.

      The gateway authentication can use a Local User Database or an Active Directory server as authentication backend. When using an Active Directory server, note the following points.

      • Both SPS and SPP must use the same server, and be the member of the same domain as the Active Directory server.

      • SPP does not support every type of Active Directory settings that SPS does. Verify that you can configure both appliances to access and retrieve data from the Active Directory server.

      • SPS does not receive the domain of the authenticated user from the Domain Controller. SPS assumes that the user belongs to the same domain that SPS is joined into. (Configuring trust between the Domain Controller of SPS and the Domain Controller of the user does not solve this problem.)

  • You must use a uniform address for the target server. Use either its IPv4 address or its hostname everywhere: when configuring the Assets in SPP, the Connection Policies and Channel Policies in SPS, and also when the user sets the target address in the SSH/RDP application. Otherwise, the authentication will fail.

To configure SPS for Sessions-initiated workflow

Configure Connection Policies on SPS to audit your sessions. Note that you have to complete these steps for each Connection Policy that uses SPP as a Credential Store. For the general steps on configuring Connection Policies, see Configuring connections.

  1. Select Credential Store > safeguard_default.

  2. Select Usermapping policy > safeguard_default.

  3. Configure gateway authentication. The users must perform gateway authentication on SPS with the same username they have Entitlements for in SPP. For details, see Configuring gateway authentication.

  4. When you are using an Approve/deny workflow on SPP, increase the Idle timeout setting of the Connection Policy. SPS will wait for an approval from SPP until half the time set in Idle timeout. For example, if the authorizer on SPP has 2 minutes to approve the access request, set the Idle timeout option on SPS to more than double this value, for example, 5 minutes.

Configuring SPS for SRA-initiated workflow

To configure SPS to use SRA in Sessions-initiated (SPS-initiated) workflows, complete the following steps.

NOTE: Only SSH and RDP sessions are supported.

Prerequisites

  • Minimum versions:

    • SPP version 2.8

    • SPS version 6.2 and newer, including 6.0.2 and newer versions of the 6.0.x branch, but excluding 6.1.x

  • You must have built an SPS cluster by promoting an SPS node to the role of Central Management node, even if it is a single node. For more information, see Creating a cluster.

CAUTION: When linking your One Identity Safeguard for Privileged Sessions (SPS) deployment to your One Identity Safeguard for Privileged Passwords (SPP) deployment, ensure that the SPS and SPP versions match exactly, and you keep the versions synchronized during an upgrade. For example, you can only link SPS version 6.6 to SPP version 6.6, and if you upgrade SPS to version 6.7, you must also upgrade SPP to 6.7.

Make sure that you do not mix Long Term Supported (LTS) and feature releases. For example, do not link an SPS version 6.0 to an SPP version 6.1.

  • You cannot use gateway authentication on SPS. For more information, see Configuring gateway authentication.

  • For RDP sessions, you must not configure SPS to act as a Remote Desktop Gateway. For more information, see Using One Identity Safeguard for Privileged Sessions (SPS) as a Remote Desktop Gateway.

  • You must use a uniform address for the target server. Use either its IPv4 address or its hostname everywhere: when configuring the Assets in SPP, the Connection Policies and Channel Policies in SPS, and also when the user sets the target address in the SSH/RDP application. Otherwise, the authentication will fail.

  • Enable SRA on Basic Settings > Starling Integration > Remote Access > Enable Remote Access.

To configure SPS for SRA-initiated workflow

  1. Download the SRA initiated plugin, then upload and configure the plugin as required.

    For more information, see Using a custom Authentication and Authorization plugin to authenticate on the target hosts.

  2. Navigate to Traffic Controls > Protocol name > Connections and create a new connection.

    Configure Connection Policies on SPS to audit your sessions. Note that you have to complete these steps for each Connection Policy that uses SPP as a Credential Store. For the general steps on configuring Connection Policies, see Configuring connections.

  3. Select Credential Store > safeguard_default.

  4. For AA plugin, select the SRA plugin configuration instance you have uploaded.

  5. Select Usermapping policy > safeguard_default.

  6. Ensure that Act as a Remote Desktop Gateway and Require Gateway Authentication on the SPS Web Interface are cleared.

  7. Navigate to Traffic Controls > Protocol name > Settings.

    When you are using an Approve/deny workflow on SPP, increase the Idle timeout setting of the Connection Policy. SPS will wait for an approval from SPP until half the time set in Idle timeout. For example, if the authorizer on SPP has 2 minutes to approve the access request, set the Idle timeout option on SPS to more than double this value, for example, 5 minutes.

Linking SPS to SPP

You can link your One Identity Safeguard for Privileged Sessions (SPS) deployment to your One Identity Safeguard for Privileged Passwords (SPP) deployment.

IMPORTANT: Once performed, you cannot unlink the SPS and SPP deployments.

If the primary IP address of your SPS deployment or SPP deployment changes, you must repeat this procedure to relink the clusters. To repeat the procedure to relink the clusters, navigate to Basic Settings > Cluster management and click Relink SPP cluster.

Prerequisites

Before you start linking your SPS deployment to your SPP deployment, consider the following:

  • Your SPS deployment must be in an SPS cluster, set as a Central management node. Even if your SPS deployment consists of a single, standalone node, you must assign the Central management role to its own single-node cluster. For details, see Managing One Identity Safeguard for Privileged Sessions (SPS) clusters.

    Configuration synchronization must be enabled between the nodes of the SPS cluster. This is required so that SPP entitlements work properly for each SPS node.

    NOTE: If you have multiple standalone SPS appliances, consider joining them to a cluster before linking SPP. In general, One Identity recommends creating a cluster if the nodes can use a common configuration, or later you might want to centrally search the data of every node. Creating a cluster from the SPS nodes after linking SPP is problematic and should be avoided.

  • You will need the primary IP address or the hostname of your SPP deployment that SPS can use to access SPP. Only IPv4 addresses are supported.

  • You will need the username and password to an SPP account with "Appliance" and "Operations" permissions.

  • Verify that your SPS policies do not contain the safeguard_default string in their names. During the linking process, SPS automatically creates and configures several policies and plugins. The name of these policies usually contains the string safeguard_default. Existing policies with such names will be overwritten.

  • The SPP and SPS nodes must be able to communicate on the TCP 8649 port. If needed, update your firewall policies.

    NOTE: When updating your firewall policies to enable the connection between SPS and SPP nodes, consider the following:

    • Connecting SPS nodes to SPS nodes: Make sure that between all the SPS nodes, the 500 and 4500 UDP ports are opened bidirectionally. This is required so that every node can initiate and accept connections from every other node through the mentioned ports.

    • Connecting SPP nodes to SPP nodes: For more information, see Enrolling replicas into a cluster in the One Identity Safeguard for Privileged Passwords Administration Guide.

    • Connecting SPS nodes to SPP nodes: Make sure that between all the SPS and SPP nodes, the 8649 TCP port is opened bidirectionally. This is required so that every node can initiate and accept connections from every other node through the mentioned port. If there are M SPP and N SPS nodes in your setup, then create M × N × 2 firewall rules to link the SPS nodes to the SPP nodes.

  • During the linking process, SPS must be able to access SPP using HTTPS on the TCP 443 port. This is required only once during the linking process. If needed, update your firewall policies.

To link your SPS deployment to SPP

  1. (Optional) Create a configuration backup of SPS. For details, see Creating configuration backups.

  2. (Optional) Create a configuration backup of SPP. For details, see the Safeguard for Privileged Passwords Administration Guide, Backup and Retention settings.

  3. Login to the Central management node of your SPS cluster. This node has Central management listed in the Basic Settings > Cluster management > Roles column.

  4. Navigate to Basic Settings > Cluster management, and click Link to SPP Cluster.

    Figure 388: Basic Settings > Cluster management — Linking SPS to SPP

    The Link Appliance to SPP dialog then appears.

    Figure 389: Basic Settings > Cluster management > Link to SPP Cluster — The Link Appliance to SPP dialog

  5. Enter the primary IP address of SPP in the SPP Address field.

    NOTE: Only IPv4 addresses are supported.

  6. Click Link. Wait until you are redirected to SPP.

  7. Login to SPP. Wait until you are redirected to SPS.

  8. Wait until SPS creates and configures the policies and plugins required for the joint operation of SPS and SPP. This step can usually take up to a minute.

  9. You will receive a message:

    • If the linking is unsuccessful, this message displays: Request failed.

      If this happens, check the credentials and the IP address that you provided.

      For details on resolving errors, see SPP to SPS link issues and SPP to SPS link error resolution.

    • If the linking is successful, this message displays: SPS successfully linked to SPP.

      SPP automatically closes any open access requests.

  10. Log out from the SPS web interface.

 Caution:

If the primary IP address of your SPS or SPP changes, you must repeat the linking procedure to relink the clusters. Use the Relink SPP cluster button to do so.

Switching seamlessly between SPS and SPP

You can seamlessly switch between the SPS and SPP web interfaces using the icon located next to the user menu. Seamless switching uses a federated login method, which enables you to switch between SPS and SPP appliances without having to reenter your credentials.

Prerequisites

  • SPP is joined to SPS, for more information, see Linking SPS to SPP.

  • On SPP, when you create an external federation, unselect the Require User to Always Authenticate check box. If you select the Require User to Always Authenticate check box, you will always be required to enter your credentials on the external provider. For more information on SPP external federation settings, see External Federation settings in the One Identity Safeguard for Privileged Passwords Administration Guide.

To set up seamless switching between SPS and SPP

  1. Complete the steps listed in Authenticating users with SAML2 login method.

    In Script name, enter the Login Provider ID of SPP.

    NOTE: The Login Provider ID is case sensitive.

  2. If you are editing the same SAML2 login method that you are currently using, after editing the method, log out and log in again for the changes to take effect.

  3. Select the icon, and after that select the logo of SPP under Linked Products.

    You have now switched to the SPP appliance.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级