Upload a certificate generated by an external PKI system to One Identity Safeguard for Privileged Sessions (SPS).
Prerequisites
The certificate to upload. For the TSA X.509 Certificate and Server X.509 Certificate, the private key of the certificate is needed as well. The certificates must meet the following requirements:
-
SPS accepts certificates in PEM format. The DER format is currently not supported.
-
SPS accepts private keys in PEM format, using RSA, DSA, and EC private key algorithms. Password-protected private keys are also supported.
NOTE: SPS accepts passwords that are not longer than 150 characters and supports the following characters:
For the internal CA certificate of SPS, uploading the private key is not required.
-
For the TSA certificate, the X509v3 Extended Key Usage extension must be set to critical with the value Time Stamping. Also, the Key Usage extension must be non repudiation and digital signature (that is, without key encipherment or other key usage).
-
For the Server certificate, the X509v3 Extended Key Usage extension must be set to TLS Web Server Authentication. Also, the Common Name of the certificate must contain the domain name or the IP address of the SPS host. If the web interface is accessible from multiple interfaces or IP addresses, list every IP address using the Subject Alt Name extension.
-
For the certificate used to sign audit trails, the X509v3 Extended Key Usage extension must be set to Sign (downloadable) executable code.
TIP: One Identity recommends using 2048-bit RSA keys (or stronger).
To upload a certificate generated by an external PKI system to SPS
-
Navigate to Basic Settings > Management > SSL certificates.
-
Click 
to upload the new certificate. A pop-up window is displayed.
Figure 142: Basic Settings > Management > SSL certificates — Uploading certificates
Select Browse, select the file containing the certificate, and click Upload.
For the Server X.509 Certificate
For the Server X.509 Certificate, you can also upload a certificate chain. For that, copy the certificates after each other in a single file. Alternatively, you can copy and paste the certificates one by one after each other into the Certificate field and click Set. The certificates do not have to be in order, SPS will order them and validate the chain: if a member of the chain is missing, an error message is displayed.
NOTE: Certificate chains are supported only for the Server X.509 Certificate.
-
To upload the private key corresponding to the certificate, click icon. A pop-up window is displayed.
Figure 143: Basic Settings > Management > SSL certificates — Uploading the private key
Select Browse, select the file containing the private key, provide the Password if the key is password-protected, and click Upload. Alternatively, you can also copy-paste the private key into the Key field, provide the Password there, and click Set.
In the case of a certificate chain, the private key has to be the same as the bottom level certificate.
Expected result
The new certificate is uploaded. If you receive the Certificate issuer mismatch error message after importing a certificate, you must import the CA certificate which signed the certificate as well (the private key of the CA certificate is not mandatory).
NOTE: To download previously uploaded certificates, click on the certificate and either download the certificate (or certificate chain) in one single PEM or DER file, or you can download single certificate files separately (if it is a certificate chain).
To generate a TSA certificate with Windows Certificate Authority (CA) that works with One Identity Safeguard for Privileged Sessions (SPS), generate a CSR (certificate signing request) on a computer running OpenSSL and sign it with Windows CA, then import this certificate into SPS for timestamping.
Prerequisites
A valid configuration file for OpenSSL with the following extensions:
[ tsa_cert ]
extendedKeyUsage = critical,timeStamping
TIP: You can copy /etc/xcb/openssl-ca.cnf from SPS to the computer that will be used for signing. Rename the file to openssl-temp.cnf.
The TSA certificate is considered valid, in terms of compatibility with SPS, if the following conditions are met:
-
The X509v3 Extended Key Usage extension of the TSA certificate is set to critical with the value Time Stamping.
-
The Key Usage extension is non repudiation and digital signature (that is, without key encipherment or other key usage).
|
|
Caution:
In Encryption, do not select Allow key exchange only with key encryption (key encipherment), because it will result in errors. |
The following X509v3 extensions are supported:
-
Hard requirement:
X509v3 Extended Key Usage must be critical, and must only contain Time Stamping.
-
Optional:
X509v3 Key Usage, if present, must be digitalSignature and/or nonRepudiation.
To generate TSA certificate with Windows Certificate Authority on Windows Server 2016 or later
-
Create CSR using the new configuration file: openssl req -set_serial 0 -config openssl-temp.cnf -reqexts tsa_cert -new -newkey rsa:2048 -keyout timestamp.key -out timestamp.csr -nodes
-
Complete the required fields according to your environment:
Generating a 2048 bit RSA private key
........................+++
......................................+++
writing new private key to 'timestamp.key'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) []:New York
Locality Name (eg, city) []:New York
Organization Name (eg, company) [Internet Widgits Pty Ltd]:Examplecompany IT Security
Organizational Unit Name (eg, section) []:Service Delivery
Common Name (eg, YOUR name) []:scb35-1-i1.tohuvabohu.examplecompany
Email Address []:vlad@examplecompany.com
-
Create and configure a time stamping web server template in the Certificate Authority, and use that to generate the TSA certificate.
-
Start the Certification Authority Microsoft Management Console, and select the CA server.
-
Right-click on Certificate Templates, and choose Manage.
Figure 144: Managing certificate templates
The Certificate Templates Console opens.
-
Right-click the Web Server template, and choose Duplicate Template.
Figure 145: Duplicating a Template
The Properties of New Template window is displayed.
-
Make the following changes to the new template:
-
On the General tab, change the Template display name to TSA.
Figure 146: Creating the new template
-
On the Request Handling tab, enable the Allow private key to be exported option.
-
On the Extensions tab, make the following changes:
Edit Application Policies
Select Application Policies and click Edit below the list of extensions.
Figure 147: Editing Application Policies
Remove Server Authentication
Select Server Authentication and click Remove.
Figure 148: Removing Server Authentication
Add Time Stamping
Click Add, select Time Stamping and click OK.
Figure 149: Adding Time Stamping
Make Time Stamping critical
Select Time Stamping and enable the Make this extension critical option, then click OK.
Figure 150: Making Time Stamping critical
Time Stamping and Critical extension are listed in the Description of Application Policies.
Figure 151: Description of Application Policies
Edit Key Usage
Select Key usage, click Edit. Enable the Signature is proof of origin (nonrepudiation) option.
Select Allow key exchange without key encryption (key agreement).
Click OK.
Figure 152: Editing Key Usage
The following are listed in the Description of Key Usage.
Figure 153: Description of Key Usage
-
On the Security tab, select Authenticated Users, and set Enroll to Allow.
Figure 154: Configuring permissions for the template
-
Click Apply. Click OK. The new TSA template is now displayed in the list of templates.
Figure 155: The new TSA template is now displayed in the list of templates
-
Close this window and return to the Certification Authority main screen, and select the Certificate Templates folder.
Figure 156: Certificate Templates
Right-click under the list, and choose New > Certificate Template to Issue.
Figure 157: Certificate Template to Issue
The Enable Certificate Templates window is displayed.
Figure 158: Enable the new template
-
Select the TSA certificate template, and choose OK. Close this window.
-
Open the command line, and issue the following command:
certreq -submit -attrib "CertificateTemplate:TSA" <CSR>
Replace <CSR> with the full path of the CSR created earlier (in the second step).
-
The Certification Authority List is displayed. Select the CA.
-
The Save Certificate window is displayed. Choose an output folder.
The certificate is generated to the specified folder.
-
In SPS, navigate to Basic Settings > Management > SSL certificates.
-
Click next to TSA X.509 certificate, browse for the previously generated certificate, and click Upload.
-
Click next to TSA private key, browse for the previously generated key, and click Upload.
NOTE: If the root CA (the CA X.509 certificate field under Basic Settings > Management > SSL certificates) that is used for other certificates on SPS is different from the CA that was used to sign the TSA certificate, a warning is displayed. In this scenario, ignore this warning.
General connection settings
Connections determine if a server can be accessed from a particular client.
-
The policies used in the connection definition can restrict the availability of the connection based on the user name, time, authentication method, and so on. Channel policies (see Creating and editing channel policies) determine if a particular channel can be used within an already established connection.
-
The policies used in the channel policy can restrict the availability of the channel based on the server and the client IP address, user name, and so on. The types of policies available in a connection depend on the protocol (SSH, RDP, and so on) enabled in the connection.
SPS compares the connection policies to the parameters of the connection request one-by-one, starting with the first policy in the policy list. SPS applies to the connection the first connection policy that completely matches the connection request.
This section describes how to configure connections, and details the general configuration options and policies that apply to every type of connection that SPS can control: HTTP, ICA, RDP, SSH, Telnet, and VNC. For a detailed list of supported protocol versions, see Supported protocols and client applications.
Protocol-specific configuration options are described in their respective sections: HTTP-specific settings, ICA-specific settings, RDP-specific settings, SSH-specific settings, Telnet-specific settings, and VNC-specific settings.
This section describes how to configure connections.
NOTE:
When configuring HTTP or SSH connections, avoid using the IP address configured for administrator or user login on SPS.
To configure connections
-
Select the type of connection from the main menu.
-
To configure an HTTP connection, select HTTP Control > Connections.
-
To configure an ICA connection, select ICA Control > Connections.
-
To configure a Remote Desktop connection, select RDP Control > Connections.
-
To configure a Secure Shell connection, select SSH Control > Connections.
-
To configure a Telnet connection, select Telnet Control > Connections.
-
To configure a VNC connection, select VNC Control > Connections.
-
Click 
to define a new connection and enter a name that identifies the connection (for example, admin_mainserver).
TIP: Use descriptive names that give information about the connection, for example, refer to the name of the accessible server, the allowed clients, and so on.
Figure 159: <Protocol name> Control > Connections — Configuring connections
-
In the From field, enter the IP address of the client that is permitted to access the server. To list additional clients, click .
You can use an IPv4 or an IPv6 address. To limit the IP range to the specified address, set the prefix to 32 (IPv4) or 128 (IPv6).
Alternatively, you can enter a hostname instead. SPS automatically resolves the hostname to an IP address.
NOTE: Note the following limitations:
-
To resolve the hostnames, SPS uses the Domain Name Servers set in the Basic Settings > Network > Naming > Primary DNS server and Secondary DNS server fields.
-
If the Domain Name Server returns multiple IP addresses, SPS randomly selects from the list.
-
In the To field, enter the IP address that the clients request.
You can use an IPv4 or an IPv6 address. To limit the IP range to the specified address, set the prefix to 32 (IPv4) or 128 (IPv6).
Alternatively, you can enter a hostname instead. SPS automatically resolves the hostname to an IP address.
NOTE: Note the following limitations:
-
To resolve the hostnames, SPS uses the Domain Name Servers set in the Basic Settings > Network > Naming > Primary DNS server and Secondary DNS server fields.
-
If the Domain Name Server returns multiple IP addresses, SPS randomly selects from the list.
-
In non-transparent mode, enter the IP address of an SPS logical interface.
For more information on setting up logical network interfaces on SPS, see Managing logical interfaces.
For more information, see Non-transparent mode.
-
In transparent mode, enter the IP address of the protected server.
For more information, see Transparent mode.
To add additional IP addresses, click .
-
If the clients use a custom port to address the server instead of the default port of the protocol, in the Port field, enter the port number that the clients request. To list additional port numbers, click .
NOTE: SPS can handle a maximum of 15 unique ports per connection policy. If you want to add more than 15 custom ports, create additional connection policies.
-
Non-transparent mode: In the Target field, enter the IP address and port number of the target server. SPS connects all incoming client-side connections to this server.
For details on organizing connections in non-transparent mode, see Organizing connections in non-transparent mode.
Figure 160: <Protocol name> Control > Connections — Configuring non-transparent connections
-
If needed, configure advanced settings (for example, network address translation, channel policy, gateway authentication, various policies, or other settings).
-
To save the connection, click Commit.
TIP: To temporarily disable a connection, deselect the checkbox of the connection.
-
If needed, reorder the list of the connection policies. You can move connection policies by clicking the 
and 
buttons.
SPS compares the connection policies to the parameters of the connection request one-by-one, starting with the first policy in the policy list. SPS applies to the connection the first connection policy that completely matches the connection request.
-
Depending on your needs and on your environment, you can configure the following settings for your connections:
-
Modify the destination or source addresses of the connections.
For more information, see Modifying the destination address and Modifying the source address.
-
Select a Backup Policy and an Archiving Policy for the audit trails and indexes of the connection.
For more information on creating backup and archive policies, see Data and configuration backups and Archiving.
If you have indexed trails, the index is archived every 30 days.
|
|
Caution:
Hazard of data loss! Make sure you also back up your data besides archiving it.
For more information, see Data and configuration backups.
If a system crash occurs, you can lose up to 30 days of index, since the index is only archived every 30 days. |
NOTE: The backup and archive policies set for the connection apply only to the audit trails and indexes of the connection. General data about the connections that is displayed on the Search page is archived and backed up as part of the system-backup process of SPS.
-
To timestamp, encrypt, or sign the audit trails, configure an Audit Policy to suit your needs.
For more information, see Audit policies.
|
|
Caution:
In RDP connections, if the client uses the Windows login screen to authenticate on the server, the password of the client is visible in the audit trail. To avoid displaying the password when replaying the audit trail, encrypt the upstream traffic in the audit trail using a separate certificate from the downstream traffic.
For more information, see Encrypting audit trails in the Administration Guide. |
-
Require the users to authenticate themselves not only on the target server, but on SPS as well.
For more information, see Configuring gateway authentication.
-
Require four-eyes authorization on the connections, with the possibility of an auditor monitoring the connection in real-time.
For more information, see Configuring four-eyes authorization.
-
In the case of certain connections and scenarios (for example SSH authentication, gateway authentication, Network Level Authentication (NLA) connections), SPS can authenticate you to an LDAP database, or retrieve your group memberships. To use these features, select an LDAP Server.
For more information, see Authenticating users to an LDAP server.
NOTE: To display the usergroups that can access a specific Connection Policy, open the Connection Policy, then on the Connections page, select Show connection permissions > Show.
-
To limit the number of new connection requests accepted from a single client IP address per minute, in the Connection rate limit field, enter the maximum number of accepted connections.
-
If you have joined an SPP appliance to SPS and want to share specific SPS functions with SPP, use the Functions shared with SPP option.
For more information, see Sharing SPS functions with SPP.
To share an RDP or an SSH connection policy with SPP to initiate sessions, select Share connection policy with SPP.
For more information, see sections Sharing RDP connection policies with SPP and Sharing SSH connection policies with SPP.
NOTE: Protocol-specific configuration options are described in their respective sections:
-
If your clients and servers support it, configure the connection to use strong encryption.
-
For graphical connections, adjust the settings of your servers for optimal performance:
-
|
|
Caution:
For optimal performance and text recognition in graphical protocols, disable antialiasing on your servers. Antialiased text in the audit trails of RDP, VNC, and X11 connections is not recognized by the OCR engine of the Audit Player. The indexer service recognizes antialiased text, but its accuracy depends on the exact antialiasing settings. To properly index the trails of these connections, disable antialiasing.
Note that by default, antialiasing is enabled on Windows Vista and later versions. Antialiasing is also called font smoothing. To optimize performance, disable ClearType, which is an antialiasing technology used on Microsoft Windows. |
-
When processing RDP connections, SPS attempts to extract the username from the connection.
To ensure that your users can access the target servers only when their username is recorded, see Usernames in RDP connections.
