The following describes how to configure four-eyes authorization.
To require four-eyes authorization for a connection
-
Navigate to the Connections page of the traffic (for example to SSH Control > Connections), and select the connection policy to modify.
-
Figure 331: <Protocol name> Control > Connections > Access Control — Configuring four-eyes authorization
Navigate to Access Control and click 
.
-
Enter the name of the usergroup whose members are permitted to authorize the sessions of the connection policy into the Authorizer Group field. This group must exist on the Users & Access Control > Local User Groups page. For details on creating and managing usergroups, see Managing user rights and usergroups.
|
|
Caution:
Usernames, the names of user lists, and the names of usergroups are case sensitive. |
-
By default, the authorizer can authorize any session of the connection policy.
If the authorizer is permitted to authorize only the sessions of a certain usergroup, select Client user is > Member of, and enter the name of the userlist whose sessions the authorizer can authorize. If you use four-eyes authorization without gateway authentication, you can specify an LDAP group instead of a userlist.
|
|
Caution:
Usernames, the names of user lists, and the names of usergroups are case sensitive. |
|
|
Caution:
When using both gateway authentication and four-eyes authorization in a Connection Policy, specify the usergroup of the gateway username. The specified group must be a local or LDAP group. |
-
Set the permissions of the usergroup set in the Authorizer Group field.
-
If the Authorizer group can authorize (that is, enable) and audit (that is, monitor in real-time and download the audit trails) the sessions, select Permission > Follow&Authorize.
-
If the Authorizer group can only authorize (that is, enable) the sessions, select Permission > Authorize.
NOTE: This option is not valid for HTTP connections.
-
If the Authorizer group can only audit (that is, monitor in real-time and download the audit trails) the sessions, select Permission > Follow.
NOTE: If the Client user is > Member of field is set, the auditor can only monitor the sessions of the specified usergroup. However, if Client user is > Member of field is set, the Auditor cannot access the Search page. To avoid this problem, add another Access Control rule for the Authorizer Group without setting the Client user isfield.
The admin user of One Identity Safeguard for Privileged Sessions (SPS) can audit and authorize every connection.
-
To ensure that the client and the authorizer use different IP addresses and thus prevent self-authorization, enable Require different IP. If this is enabled, and the client and the authorizer do not have different IP addresses, it disables all actions for the connection and the four-eyes authorization, until they have different IP addresses.
-
To ensure that the client and the authorizer use different usernames and thus prevent self-authorization, enable Require different Username. If this is enabled, and the client and the authorizer do not have different usernames, it disables all actions for the connection and the four-eyes authorization, until they have different usernames.
-
Repeat steps 2-6 to add other authorizers or usergroups if needed.
-
Click 
.
-
Navigate to the Channel Policies page of the traffic (for example, to SSH Control > Channel Policies), and select the channel policy used in the connection.
Figure 332: <Protocol name> Control > Channel Policies — Configuring four-eyes authorization in the channel policy
-
Enable the Four-eyes option for the channels which should be accessed only using four-eyes authorization.
NOTE: If a connection uses secondary channels that require four-eyes authorization — for example, a Remote Desktop connection allows a Drawing channel but requires four-eyes authorization for a Disk redirection channel — the connection is locked until the authorizer accepts the channel on the Four-Eyes page of SPS, or the four-eyes request times out. During this time, the client application can become nonresponsive, for example, display the graphical desktop but not react to mouse clicks.
NOTE: In Citrix ICA connections, four-eyes authorization is required before the user logs in to the destination server. To request four-eyes authorization only after the log in, when the server-side username is already known, select the Perform 4 eyes after user login option.
-
Click . After that, users accessing connections using the modified channel policy must be authorized as described in Performing four-eyes authorization on One Identity Safeguard for Privileged Sessions (SPS).
-
(Optional) If you want to provide a limited SPS web interface to your users that can be used only for gateway authentication and 4-eyes authorization, set up a dedicated user-only web login address. For details, see Configuring user and administrator login addresses.
The following describes how to perform four-eyes authorization on One Identity Safeguard for Privileged Sessions (SPS).
To perform four-eyes authorization on SPS
-
When a user initiates a connection from a client and four-eyes authorization is required for the connection, SPS will pause the connection.
NOTE: Four-eyes authorization can be set separately for every channel. However, if a client of an existing connection opens a new channel that requires four-eyes authorization, every channel is paused until the authorization is completed.
-
Login to SPS, and select Four-Eyes from the main menu. The list of connections waiting for authorization will be displayed.
Figure 333: Four-Eyes — Performing four-eyes authorization
NOTE: Only those connections will be listed, where your usergroup has the Authorize or the Follow&Authorize permissions. No other SPS privilege is required to access this page.
-
Select the connection and click Accept to enable the connection, Reject to deny the connection, or Accept&Follow to enable it and monitor in real-time.
NOTE: Following a session requires the following:
-
The Record audit trail option must be enabled for the specific channel in the Channel policy of the connection.
-
The Audit Player application must be installed on the computer of the auditor.
-
If the Audit policy of the connection uses encryption, the appropriate decryption keys must be available on the computer of the auditor.
The Safeguard Desktop Player application replays the live streams in live mode. For details on how to monitor a connection in real-time using the Safeguard Desktop Player, see .
-
Enter a note why the connection was accepted/rejected into the appearing dialog box. This description will be stored in the connection database together with other metadata about the connection.
Figure 334: Describing why a connection was accepted/rejected
-
If you have to terminate an ongoing connection for some reason, select Active Connections from the main menu. The list of ongoing connections will be displayed.
Figure 335: Active Connections — Displaying active connections
-
Select the connection to stop, and click Terminate.
NOTE: When following a connection in the Safeguard Desktop Player application, the auditor can also terminate the connection from the Audit Player by clicking Terminate.
Figure 336: Terminating a connection in Safeguard Desktop Player
Credential Stores offer a way to store user credentials (for example, passwords, private keys, certificates) and use them to log in to the target server, without the user having access to the credentials. That way, the users only have to perform gateway authentication on SPS with their usual password (or to an LDAP database), and if the user is allowed to access the target server, SPS automatically logs in using the Credential Store.
For more information on gateway authentication, see Configuring gateway authentication.
NOTE: Keyboard-interactive authentication is not supported when using credential stores.
Figure 337: Authenticating using Credential Stores
Credential Stores can be stored locally on SPS, or on a remote device. For remote Credential Stores, SPS integrates with external authentication and authorization systems using plugins.
NOTE: After performing a successful gateway authentication, if the credential store does not contain a password for the user, the user is prompted for the server-side password as a fallback.
In case of authenticating to RDP servers using Network Level Authentication (NLA), the server-side password is prompted at the start of the connection. If there is no password in the credential store for the user and the server-side password is incorrect, the connection is terminated.
The following describes how to configure a local Credential Store that stores the credentials used to login to the target host.
Prerequisites
NOTE: Users accessing connections that use Credential Stores to authenticate on the target server must authenticate on SPS using gateway authentication or an AA plugin. Therefore gateway authentication or an AA plugin must be configured for these connections.
For more information, see and .
To configure a local Credential Store that stores the credentials used to login to the target host
-
Navigate to Policies > Credential Stores.
-
Click and enter a name for the Credential Store.
-
Select Local.
-
Select Encryption key > Built-in. That way the credentials will be encrypted with a built-in password, and the Credential Store is automatically accessible when SPS boots up. To use custom passwords to encrypt the Credential Store, see Configuring password-protected Credential Stores.
Figure 338: Policies > Credential Stores > Local — Configuring local Credential Stores
-
Add credentials to the Credential Store.
-
Click and enter the destination host and the username. For the destination host, you can use hostname, IP address, or subnet as well. To use the same credentials for every destination host, enter the 0.0.0.0/0 subnet. To use the credentials only on the hosts of a specific domain, enter *.domain. Note that:
-
Usernames are case sensitive.
-
To authenticate users of a Windows domain, enter the name of the domain into the Host field.
Use an IPv4 address.
-
Set the credentials. SPS will use these credentials to login to the destination host if the credential store is selected in a Connection policy. If more than one credential is specified to a host-username pair, SPS will attempt to use the credentials as the destination host requests it.
-
To add a password, click Passwords > , then enter the password corresponding to the username.
-
To upload a private key, click SSH Keys > >
, then paste or upload a private key.
NOTE: If the private key is protected by a passphrase, enter the passphrase. The passphrase is needed only once during the upload, it is not required for the later operation of the Credential Store.
-
To generate a keypair on SPS click SSH Keys > > , set the length and type of the key, then click Generate. After that, click the fingerprint of the key to download the public part of the keypair. There is no way to download the private key from the SPS web interface.
NOTE:
TIP: One Identity recommends using 2048-bit RSA keys (or stronger).
-
To upload a certificate and the corresponding private key, click X509 Keys > > , then paste or upload a certificate and the private key.
NOTE: If the private key is protected by a passphrase, enter the passphrase. The passphrase is needed only once during the upload, it is not required for the later operation of the Credential Store.
NOTE: SPS accepts passwords that are not longer than 150 characters and supports the following characters:
-
Repeat the previous step to add further credentials to the username as necessary.
-
Repeat the previous step to add further hosts or usernames as necessary.
NOTE: Credential Stores can be used together with usermapping policies to simplify the administration of users on the target hosts.
For more information, see Configuring usermapping policies.
-
Click .
-
Navigate to the Connection policy where you want to use the Credential Store (for example, to SSH Control > Connections), select the Credential Store to use in the Credential Store field, then click .
NOTE: The Connection Policy will ignore the settings for server-side authentication (set under Relayed authentication methods) if a Credential Store is used in the Connection Policy.
Figure 339: <Protocol name> Control > Connections — Select a Credential Store to use
