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.
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 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.
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
(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 column.
Navigate to Basic Settings > Cluster management, and click Link to SPP Cluster.
Figure 382: Basic Settings > Cluster management — Linking SPS to SPP
The Link Appliance to SPP dialog then appears.
Figure 383: Basic Settings > Cluster management > Link to SPP Cluster — The Link Appliance to SPP dialog
Enter the primary IP address of SPP in the SPP Address field.
NOTE: Only IPv4 addresses are supported.
Click Link. 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 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.
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. |
Common linking error resolutions follow which may occur when linking SPS (SPP) to One Identity Safeguard for Privileged Sessions (SPS).
Error: The browser reports errors when SPS redirects to SPP's login page, for example, This site can’t be reached. The exact error message depends on the browser.
Resolution: Click the Back button of the browser and enter the correct address into the SPP Address field.
Error: After clicking the Join button, a web site other than SPP's Login interface is displayed.
Resolution: Click the Back button of the browser and enter the correct address into the SPP Address field.
Error message: Error joining to SPP: SPS has failed to join to SPP. For more information, see the error details. (JoinFailed)
Raw error:
{ "response": "Error sending request: SSLError: HTTPSConnectionPool(host='examplespp.company', port=443): Max retries exceeded with url: /service/core/v3/Cluster/SessionModules (Caused by SSLError(CertificateError(\"hostname 'examplespp.company' doesn't match '192.0.2.123'\",),))", "status": null, "url": "https://examplespp.company/service/core/v3/Cluster/SessionModules" }
Resolution:
If SPP's certificate contains SPP's IPv4 address in the Common Name or subjectAltName field, then enter that IP address when linking SPS to SPP.
If SPP's certificate contains only its DNS name in the Common Name or subjectAltName field, then use that hostname when linking SPS to SPP.
Otherwise, set up an SSL server certificate for SPP which matches its IP address in the certificate's Common Name or subjectAltNamefields (see SSL Certificates in the Safeguard Administration Guide) and retry linking. Wait about five minutes to let the timeout of the failed link request expire before starting a new link request after a failed incomplete one. (Alternatively, see Reversing the SPP to SPS join in the Safeguard Administration Guide.)
Error: Login to the SPP web interface fails.
Raw error:
{ "error": "invalid_request", "error_description": "Access denied.", "success": false }
Error message: Error joining to SPP: SPS has failed to join to SPP. For more information, see the error details. (JoinFailed)
Authorization is required for this request. Code: 60108 URL: https://192.0.2.123/service/core/v3/Cluster/SessionModules Status: 403
Error message: Error joining to SPP: SPS has failed to join to SPP. For more information, see the error details. (JoinFailed)
The session connection has a missing, invalid, or non-unique value [ NodeId ]. Code: 60657 URL: https://192.0.2.123/service/core/v3/Cluster/SessionModules Status: 400
ERROR: Request to https://192.0.2.123/service/a2a/v2/PsmValidation failed, response (HTTP 403):
{ "Code": 60108, "Message": "Authorization is required for this request.", "InnerError": null }
In addition to the monitoring tools in Safeguard for Privileged Passwords (SPP), you can use the SPP to SPS link issues during the linking process. Several SPS tools are described below.
If the linking process fails for any reason, consult the system logs.
To view the Safeguard for Privileged Sessions logs, navigate to Basic Settings > Troubleshooting > View log files.
To show only the logs for the linking process:
Use the buttons at the bottom of the dialog to perform the following tasks:
To increase the level of detail in the log, enable debug level logging:
When SPP and SPS report a successful linking, but the connections do not work, view the SPS connection logs.
In Safeguard for Privileged Sessions, navigate to Basic Settings > Troubleshooting > View log files.
To show only the logs for the linking process:
To change the verbosity level of SPS, complete the following steps in Safeguard for Privileged Sessions:
Select the desired log level from the Verbosity level field. The verbosity level ranges from 1 (no logging) to 10 (extremely detailed), with level 4 being the default normal level.
|
CAUTION: High verbosity levels generate a very large amount of log messages and might result in a very high load on the machine. Log levels set around 9 to 10, may result in logs with highly sensitive data, for example, passwords in plain text format. |
You can use the Diagnostics tools of SPP and SPS to test network issues. The following commands are available:
To execute one of the above commands on SPS, see Network troubleshooting.
To execute one of the above commands on SPP, see Diagnostics tools of SPP.
If you have an issue which needs Support assistance, you may be asked to provide an SPS Support Bundle. To collect system-state information (also known as a debug bundle) in One Identity Safeguard for Privileged Sessions, see Collecting logs and system information for error reporting.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy