One Identity Safeguard for Privileged Sessions 7.5 - Administration Guide

Prerequisites

• The target servers and SPS must be in the same domain, or you must establish trust between the domains that contain the target servers and SPS. For details on the type of trust required, see Using One Identity Safeguard for Privileged Sessions (SPS) across multiple domains in the Administration Guide.

To use NLA with domain membership

1. Navigate to Traffic Controls > RDP > Settings, and select the RDP settings policy that you use in your connection policies.

2. Select the Enable Network Level Authentication > Require domain membership option.

3. Navigate to Traffic Controls > RDP > Domain membership.

4. Enter the name of the domain (for example mydomain) into the Domain field.

   Figure 216: Traffic Controls > RDP > Domain membership — Joining a domain

   

5. Enter the name of the realm (for example mydomain.example.com) into the Full domain name field.

   NOTE: Ensure that your DNS settings are correct and that the full domain name can be resolved from SPS. To check this, navigate to Basic Settings > Troubleshooting > Ping, enter the full domain name into the Hostname field, and select Ping host.

6. Click .

7. Click Join domain. A pop-up window is displayed.

8. SPS requires an account to your domain to be able to join the domain. Enter the following information:

   • The name of the user into the Username field.

   • The password into the Password field.

     NOTE: SPS accepts passwords that are not longer than 150 characters and supports the following characters:

     • Letters A-Z, a-z

     • Numbers 0-9

     • The space character

     • Special characters: !"#$%&'()*+,-./:;<>=?@[]\^-`{}_|

   • The name of your domain controller into the Domain controller field. If you leave this field blank, SPS tries to find the domain controller automatically.

     NOTE: Ensure that your DNS settings are correct and that the hostname of the domain controller can be resolved from SPS. To check this, navigate to Basic Settings > Troubleshooting > Ping, enter the name of the domain controller into the Hostname field, and select Ping host.

   • The organizational unit (OU) into the Organization unit field.

     The OU string reads from top to bottom without RDNs, and is delimited by a '/'. Note that '\' is used for escape by both the shell and ldap, so it may need to be doubled or quadrupled to pass through, and it is not used as a delimiter.

9. Click Join domain.

10. If successful, SPS displays the name of the domain it joined.

    NOTE: If you need SPS to leave the domain for some reason, click Leave domain.

To accept only verified certificates

1. Create a list of trusted CA certificates that you will use to verify the certificate of the server. For details, see Verifying certificates with Certificate Authorities.

2. Navigate to Traffic Controls > RDP > Connections and select the connection policy to modify.

3. Select TLS.

4. Select the required option under Server certificate validation.

   You have the following options:

   • No validation.

   • Only accept certificates authenticated by the trusted CA list.

   NOTE: The Only accept certificates authenticated by the trusted CA list. option has no effect if the session uses Network Level Authentication, because in such cases SPS uses a different method to validate the server certificate.

   If you use Network Level Authentication (NLA, also called CredSSP), there is no verification performed in the TLS layer due to the TLS session-binding. For more information on TLS session-binding, see section [MS-CSSP]: Credential Security Support Provider (CredSSP) Protocol in the Microsoft documentation.

   Figure 217: Traffic Controls > RDP > Connections — Using SSL-encryption in RDP connections

   

5. (Optional) If you selected Only accept certificates authenticated by the trusted CA list., in Trusted CA list, select the CA list to use for verifying the certificate of the server.

6. Click Commit.

7. (Optional) Configure your Windows servers to display a certificate signed with the above Certificate Authority for incoming RDP connections. To do this, complete the following steps:

   1. Generate a certificate that contains the IP address or the hostname of the target server in its Common Name (CN) field and sign it with the Certificate Authority whose certificate you added to the Trusted CA list of SPS.

   2. Convert the signed certificate of the target server to PKCS12 format that includes the private key.

   3. Start the Microsoft Management Console (MMC) on the target server and select Add Snap-in > Certificates > Computer Account.

   4. Right-click the Personal store, then select All Tasks > Import, and select the certificate created for the server.

   5. Complete the Certificate Import Wizard, but do not select the Extended certificate properties option.

   6. Select Start > Administrative tools > Remote Desktop > Remote Desktop Session Host Configuration.

   7. Right-click the connection you want to configure and select Properties > General.

   8. Set the Security layer to SSL.

   9. Click Certificate > Select and select the imported certificate. The server uses this certificate to verify its identity for the incoming RDP connections.