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:
Auto-approved access request
Approved/denied access request (similar to the four-eyes authorization feature of SPS)
Figure 346: Sessions-initiated (SPS-initiated) workflow
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.
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 the Sessions-initiated (SPS-initiated) workflow
On SPS, join SPP and SPS as described in Joining SPS to SPP.
Configure SPP to allow SPP to request passwords from SPP as described in Configuring SPP for Sessions-initiated workflow.
Configure SPS to use the joined SPP as a Credential Store as described in Configuring SPS for Sessions-initiated workflow.
Optionally, customize monitoring settings as follows:
To configure SPP to use the joined SPS in Sessions-initiated (SPS-initiated) workflows, complete the following steps. For details on the workflow, see Using SPS with SPP.
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.
To configure SPP for Sessions-initiated workflow
On SPP, navigate to Administrative Tools > Settings > Session Management.
Click Session Module Password Access Enabled to enable this feature. A dialog opens.
Type Enable.
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.
Ensure that these users have the proper Entitlements to access the passwords to their target servers. Otherwise, SPS will reject their sessions.
To configure SPS to use the joined SPP in Sessions-initiated (SPS-initiated) workflows, complete the following steps. For details on the workflow, see Using SPS with SPP.
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.
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.
Select Credential Store > safeguard_default
Select AA plugin > safeguard_default
Select Usermapping policy > safeguard_default
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.
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.
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.
Your SPS deployment must be a SPS cluster (set as 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.
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.
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
(Optional) Create a configuration backup of SPS. For details, see Creating configuration backups.
(Optional) Create a configuration backup of SPP. For details, see the Safeguard for Privileged Passwords Administration Guide, Backup and Retention settings.
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 347: Basic Settings > Cluster management — Joining SPS to SPP
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.
Click Join. Wait until you are redirected to SPP.
Login to SPP. Wait until you are redirected to SPS.
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.
You will receive a message:
If the join is unsuccessful, this message displays: Request failed. Check the credentials and the IP address you provided. For details on resolving errors, see SPP to SPS join issues and SPP to SPS join error resolution
If the join is successful, this message displays: SPS successfully joined to SPP. SPP automatically closes any open access requests.
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. |
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy