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

One Identity Safeguard for Privileged Sessions 6.0.14 LTS - Administration Guide

Preface Introduction The concepts of 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 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) 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 Appendix: Deprecated features Glossary

Configuring the Sessions-initiated workflow

Sessions-initiated (SPS-initiated) workflow

In the Sessions-initiated workflow, the users initiate sessions from SPS. In this workflow SPS uses SPP as a credential store.

This workflow is transparent in the sense that you can connect to the target server or to SPS directly using your SSH or RDP client application. SPS authenticates these clients and communicates with SPP to get the password for the target server. It then uses that password to open the connection. Authentication happens on SPS, while authorization happens on SPP based on the user's entitlements.

This is what old and new users of standalone SPS are likely to prefer.

The usual SPP Access Requests workflows that SPP provides are supported:

To configure the Sessions-initiated (SPS-initiated) workflow

  1. On SPS, link SPP and SPS as described in Joining SPS to SPP.

  2. Configure SPP to allow SPS to request passwords from SPP as described in Configuring SPP for Sessions-initiated workflow.

  3. Configure SPS to use the linked SPP as a Credential Store as described in Configuring SPS for Sessions-initiated workflow.

  4. Optionally, customize monitoring settings as follows:

Configuring SPP for Sessions-initiated workflow

To configure SPP to use the linked SPS 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 the Central Management node, even if it is a single node. For more information, see Building 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.

To configure SPP for Sessions-initiated workflow

  1. On SPP, navigate to Administrative Tools > Settings > Session Management.

  2. Click Session Module Password Access Enabled to enable this feature. A dialog opens.

  3. Type Enable.

  4. Ensure that SPP can access the usernames that will authenticate on the SPS gateway either from a local user database, or from an Active Directory.

  5. Ensure that these users have the proper Entitlements to access the passwords to their target servers. Otherwise, SPS will reject their sessions.

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 the Central Management node, even if it is a single node. For more information, see Building 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 AA plugin > safeguard_default

  3. Select Usermapping policy > safeguard_default

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

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

Joining SPS to SPP

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

IMPORTANT: Joining your SPS and SPP appliances is an action that you cannot undo.

If the primary IP address of your SPS or SPP changes, you must repeat this procedure to rejoin the clusters.

Prerequisites
  • Your SPS deployment must be an SPS cluster (not a high-availability cluster, but a Central Management cluster). Even if your SPS deployment consists of a single, standalone node, you must convert it to the Central Management node of its own single-node cluster. For details, see Managing Safeguard for Privileged Sessions (SPS) clusters.

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

    NOTE:

    If you have multiple standalone SPS appliances, consider joining them to a cluster before joining 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 joining 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 that has "Appliance" and "Operations" permissions.

  • Verify that your SPS policies do not contain the safeguard_default string in their names. During the join 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 join process, SPS must be able to access SPP using HTTPS on the tcp 443 port. This is required only once during the join process. If needed, update your firewall policies.

To join 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 field.

    Figure 305: Basic Settings > Cluster management — Joining SPS to SPP

  4. Navigate to Basic Settings > Cluster management > Join to SPP cluster and enter the primary IP address of SPP into the IPv4 address or hostname of SPP to join field. Only IPv4 addresses are supported.

  5. Click Join. Wait until you are redirected to SPP.

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

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

  8. You will receive a message:

  9. Log out from the SPS web interface.

Caution:

If the primary IP address of your SPS or SPP changes, you must repeat this procedure to rejoin the clusters.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级