Use the Offline Workflow page to configure automatic settings to control Offline Workflow Mode. You can manually override the automatic settings. For more information, see Manually override automatic Offline Workflow.
To configure automatic settings to control Offline Workflow Mode
- Go to Offline Workflow:
web client: Navigate to 
Cluster | Offline Workflow.
- On the Offline Workflow dialog, select Enable Automatic Offline Workflow so the appliance will be automatically placed in Offline Workflow Mode when the appliance loses connection and cannot establish consensus with the cluster for the specified number of minutes entered (see next step).
- Identify the number of Minutes after consensus is lost before the appliance is automatically switched over to Offline Workflow Mode. The Automatic Offline Workflow Threshold defaults to 15 minutes and can be changed to a minimum of five minutes or more.
- If you selected the first check box to enabled automatic Offline Workflow Mode, you can select Automatic Resume Online Workflow so the appliance automatically resumes online operations once consensus with the cluster is restored for the specified number of minutes entered (see next step).
- Identify the number of Minutes after consensus is restored that the appliance is automatically switched over to online workflow. The Automatic Resume Online Workflow Threshold defaults to 15 minutes and can be changed to a minimum of five minutes or more.
- Click Save.
Use the Offline Workflow page to manually enable offline workflow or resume online operations.
For details on either of these operations, see Manually control Offline Workflow Mode.
Before resuming online operations, see Considerations to resume online operations.
To manually Enable Offline Workflow
This option is only available when the appliance has lost consensus with the cluster.
- Go to Enable Offline Workflow:
- web client: Navigate to Cluster | Offline Workflow.
- Click
Enable Offline Workflow to manually trigger Offline Workflow Mode.
- In the dialog box, type in Enable Offline Workflow and click Enter. The appliance is in Offline Workflow Mode and enters maintenance.
- You can verify requests and view health checks on the Cluster Management window. For more information, see Cluster Management.
To manually Resume Online Operations
This option is only available when the appliance is in Offline Workflow Mode.
- Go to Offline Workflow:
- web client: Navigate to Cluster | Offline Workflow.
- Click
Resume Online Operations to manually trigger moving the appliance from Offline Workflow Mode back to online operations.
- In the dialog box, type in Resume Online Operations and click Enter.
- When maintenance is complete, select to restart. The appliance is returned to Maintenance mode.
- You can verify requests and view health checks on the Cluster Management window. For more information, see Cluster Management.
The Asset Administrator can link a Safeguard for Privileged Sessions (SPS) cluster to a Safeguard for Privileged Password (SPP) cluster of one appliance or more for session recording and auditing. The actual link must be between the SPP primary and the SPS cluster master. This means that the Safeguard for Privileged Sessions (SPS) cluster is aware of each node in an SPP cluster and vice-versa.
Once linked, all sessions are initiated by the SPP appliance via an access request and managed by the SPS appliance and sessions are recorded via the Sessions Appliance.
|
|
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 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.1 to an SPP version 6.1. |
NOTE: If you have a single node SPS cluster where the Central Management node is also the Search Master, SPP will be unable to launch sessions. There has to be at least one SPS appliance in the cluster that is capable of recording sessions. See the SPS Administration Guide, Managing Safeguard for Privileged Sessions (SPS) clusters.
Safeguard for Privileged Passwords link guidance
Before initiating the link, review the steps and considerations in the link guidance. For more information, see SPP and SPS sessions appliance link guidance.
Pay attention to the roles assigned to the SPS nodes. The following caution is offered to avoid losing session playback from SPP.
|
|
CAUTION: Do not switch the role of an SPS node from the Search Local role to Search Minion role. If you do, playback of the sessions recorded while in the Search Local role may not be played back from the SPP appliance, and may only be played back via the SPS web user interface. Recordings made with the node in Search Minion role are pushed to the Search Master node and are available for download to SPP. For details about SPS nodes and roles, see the One Identity Safeguard for Privileged Sessions Administration Guide: One Identity Safeguard for Privileged Sessions - Technical Documentation. |
Standard operating procedure after the initial link
If you add another SPS cluster after the initial link, follow these standard operating procedures:
- Add link connections. See Viewing, deleting, or editing link connections later in this topic.
-
Identify the session settings on the entitlements access request policy (SPS Connection Policy which is the IP address of the cluster master). For more information, see Creating an access request policy
- Assign the managed networks. For more information, see Managed Networks.
- Enable the Session Access Enabled toggle .
If the SPS Central Management node is down
SPP continues to launch sessions on the managed hosts when the SPS Central Management node is down. However, as long as the Central Management node is down, SPP cannot validate existing policies nor can it validate the SPS cluster topology. See the Safeguard for Privileged Sessions Administration Guide, Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster.
Connection deletion: soft delete versus hard delete
Depending on your goals, you can perform a soft delete or a hard delete.
Soft delete the connection
When a session connection is deleted, the connection information is soft deleted so that a relink of the same SPS appliance can reuse the same values. This approach of soft deleting and reusing the same connection values on a relink avoids "breaking" all of the Access Request Polices that referenced the previous session connection.
Hard delete the connection
A hard delete can be performed to permanently remove the session connection. This is usually only done in cases where either a relink is not desired or retaining the previous session connection values is preventing an SPS appliance from linking or relinking.
A hard delete can be performed from the API using the following steps for using PowerShell or Swagger.
Hard delete with PowerShell
The latest version of Safeguard PowerShell includes two cmdlets to perform the hard delete:
split-safeguardSessionCluster -SessionMaster <name or ID of session master>
Remove-SafeguardSessionSplitCluster -SessionMaster <name or ID of session master>
See OneIdentity/safeguard-ps.
Hard delete with Swagger
- In a browser, navigate to https://<your-ip-address>/service/core/swagger.
- Authenticate to the service using the Authorize button.
- Navigate to Cluster->GET /v3/cluster/SessionModules and click Try it out!.
- Identify if the unwanted session connection exists on the list:
- If the unwanted session connection exists in the list, then:
- Note the ID of the session connection.
- Navigate to Cluster DELETE /v3/cluster/SessionModules.
- Enter the ID.
- Click Try it out!”.
- Go to step 3.
- If the unwanted session connection does not exist in the list, then:
- Set the includeDisconnected parameter to true.
- Click Try it out!.
- If the unwanted session connection exists in the list, then go to step 4a to delete the entry a second time which will result in a hard delete.
- The process is complete and the session connection is permanently removed.
Viewing, deleting, or editing link connections
Once the link is complete, go to Session Appliances:
- web client: Navigate to Cluster | Session Appliances.
The Session Appliances pane displays the following session details.
Table 42: Session Appliances: Properties
|
Host Name |
The host name of the SPS appliance host cluster master. |
|
Managed Hosts |
Other nodes in the SPS cluster identified by the managed host name and IP address. Hover over any  Warning icon to see if the Managed Host is Unavailable or Unknown. |
|
Network Address |
The network DNS name or IP address of the session connection. |
|
Connection User |
The user name for Safeguard for Privileged Passwords (SPP). Do not include spaces in the user name. |
|
Thumbprint |
A unique hash value that identifies the certificate. |
|
Description |
(optional) Descriptive text about the SPS session connection (for example, 20 on cluster - 172 primary node). |
Double-click a Host Name row to bring up the Session Module Connection dialog.
Table 43: Session Module Connection: Properties
|
Node ID |
The name of the Safeguard for Privileged Sessions Appliance used to authenticate the linked SPS session connection. |
|
Host Name |
The host name of the SPS appliance host cluster master. |
|
Connection Username |
The user name for Safeguard for Privileged Passwords (SPP). Do not include spaces in the user name. |
|
Description |
(Optional) Descriptive text about the SPS session connection (for example, 20 on cluster - 172 primary node). |
|
Network Address |
The network DNS name or IP address of the session connection. |
|
Use Host Name For Launch (not IP address) |
If checked, the connection string used to launch a session uses the host name of the SPS appliance rather than the IP address. |
Use these toolbar buttons to manage sessions.
Table 44: Sessions Management: Toolbar
|
 Remove
|
Remove the selected linked SPS session connection. For details on soft versus hard deletes, see Connection deletion: soft delete versus hard delete earlier in this topic. |
 Edit |
Modify the selected linked SPS session connection Description or Network Address on the Session Module Connection dialog. |
 Refresh |
Update the list of linked SPS session connections. |
Safeguard for Privileged Passwords allows you to enable or disable access request and password and SSH key management services. These settings control password or SSH key release requests, manual account password or SSH key validation, and reset tasks, as well as the automatic profile check and change tasks in Partitions. You can also enable or disable discovery tasks, directory sync, and the Audit Log Stream Service.
Services are enabled by default except for the Audit Log Stream Service.
By default, services are disabled for service accounts and for accounts and assets found as part of a discovery job. Service accounts can be modified to adhere to these schedules and discovered accounts can be activated when managed.
It is the responsibility of the Appliance Administrator to manage these settings.
Navigate to 
Enable or Disable Services to see the settings listed below.
- Appliance Administrators can click the Disable all enabled services button to disable all services (as long as at least one service is currently enabled). A dialog will appear asking for confirmation before disabling the services.
- Click a toggle to change a setting:
toggle on and 
toggle off.
- Click Refresh to update the information on the page.
Table 45: Enable or Disable Services settings
|
Disable all enabled services |
Appliance Administrators can use this button to disable all services (as long as at least one service is currently enabled). A dialog will appear asking for confirmation before disabling the services. You will need to reenable each service individually. |
|
Requests |
|
Session Requests Enabled |
Session requests are enabled by default, indicating that authorized users can make session access requests. There is a limit of 1,000 sessions on a single access request.
Click the Session Requests toggle to disable this service so sessions can not be requested.
NOTE: When Session Requests is disabled, no new session access requests can be initiated. Depending on the access request policies that control the target asset/account, you will see a message informing you that the Session Request feature is not available.
In addition, current session access requests cannot be launched. A message appears, informing you that Session Requests is not available. For example, you may see the following message: This feature is temporarily disabled. See your appliance administrator for details. |
|
Password requests |
Password requests are enabled by default, indicating that authorized users can make password release requests
Click the Password requests toggle to disable this service so passwords can not be requested.
NOTE: Disabling the password request service will place any open requests on hold until this service is reenabled. |
|
SSH Key requests |
SSH key requests are enabled by default, indicating that authorized users can make SSH key release requests
Click the SSH Key requests toggle to disable this service so SSH keys can not be requested.
NOTE: Disabling the password request service will place any open requests on hold until this service is reenabled. |
|
Password Management |
|
Check password management |
Check password management is enabled by default, indicating that Safeguard for Privileged Passwords automatically performs the password check task if the profile is scheduled, and allows you to manually check an account's password.
Click the Check password management toggle to disable the password validation service.
NOTE: Safeguard for Privileged Passwords enables automatic password management services by default. Typically, you would only disable them during an organization-wide maintenance window.
When disabling a password management service, Safeguard for Privileged Passwords allows all currently running tasks to complete; however, no new tasks will be allowed to start. |
|
Change password management |
Change password management is enabled by default, indicating that Safeguard for Privileged Passwords automatically performs the password change task if the profile is scheduled, and allows you to manually reset an account's password.
Click the Change password management toggle to disable the password reset service.
NOTE: Safeguard for Privileged Passwords enables automatic password management services by default. Typically, you would only disable them during an organization-wide maintenance window.
When disabling a password management service, Safeguard for Privileged Passwords allows all currently running tasks to complete; however, no new tasks will be allowed to start. |
|
SSH Key Management |
|
Check SSH Key |
SSH key check is enabled by default, indicating that SSH key check is managed per the profile governing the partition's assigned assets and the assets' accounts.
Click the Check SSH Key toggle to disable the check service. |
|
Change SSH Key |
SSH key change is enabled by default, indicating that SSH key change is managed per the profile governing the partition's assigned assets and the assets' accounts.
Click the Change SSH Key toggle to disable the change service. |
|
Discovery |
|
Asset discovery |
Asset discovery is enabled by default, indicating that available Asset Discovery jobs find assets by searching directory assets, such as Active Directory, or by scanning network IP ranges. For more information, see Discovery. |
|
Account discovery |
Account discovery is enabled by default, indicating that available Account Discovery jobs find accounts by searching directory assets such as Active Directory or by scanning local account databases on Windows and Unix assets (/etc/passwd) that are associated with the account discovery job. For more information, see Discovery. |
|
Service discovery |
Service discovery is enabled by default, indicating that available Service Discovery jobs find Windows services that run as accounts managed by Safeguard. For more information, see Discovery. |
|
SSH Key discovery |
SSH key discovery is enabled by default. With the toggle on, SSH keys in managed accounts are discovered. For more information, see SSH Key Discovery. |
|
Directory |
|
Directory sync |
Directory sync is enabled by default, indicating that additions or deletions to directory assets are synchronized. You can set the number of minutes for synchronization. For more information, see Management tab (add asset). |
|
Audit |
|
|
Audit Log Stream Service |
Use this toggle to send Safeguard for Privileged Passwords data to Safeguard for Privileged Sessions (SPS) to audit the Safeguard privileged management software suite. The feature is disabled by default.
To accept SPP data, the SPS Appliance Administrator must turn on audit log syncing. For information, see the Safeguard for Privileged Sessions Administration Guide.
SPP and SPS must be linked to use this feature. For more information, see SPP and SPS sessions appliance link guidance.
While the synchronization of SPP and SPS is ongoing, SPS is not guaranteed to have all of the audit data at any given point due to some latency.
NOTE: This setting is also available under Security Policy Management | Settings. For more information, see Security Policy Settings. |
