Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 5.8.0 - Administration Guide

Preface Introduction The concepts of SPS The Welcome Wizard and the first login Basic settings User management and access control Managing SPS
Controlling SPS: reboot, shutdown Managing Safeguard for Privileged Sessions clusters Managing a high availability SPS cluster Upgrading SPS Managing the SPS license Accessing the SPS console Sealed mode Out-of-band management of SPS Managing the certificates used on SPS
General connection settings HTTP-specific settings ICA-specific settings RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search (classic) interface Using the Search interface Searching session data on a central node in a cluster Advanced authentication and authorization techniques Reports The SPS RPC API The SPS REST API SPS scenarios Troubleshooting SPS Configuring external devices Using SCP with agent-forwarding Security checklist for configuring SPS Jumplists for in-product help Third-party contributions About us

Setting up a transparent HTTP connection

Purpose:

To set up a transparent HTTP connection, perform the following steps. To audit HTTP connections in non-transparent mode, see Enabling SPS to act as a HTTP proxy.

Figure 158: HTTP Control > Connections — Transparent HTTP connection

Steps:
  1. In the Name field, enter the name of the connection that will identify the connection policy.

  2. In the From field, enter the IP address and prefix of the client that will be permitted to access the server.

    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).

  3. In the To field, enter the IP address and prefix that the clients will target.

    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).

  4. In the Target section, select Use original target address of the client.

  5. In the SNAT section, select Use the original IP address of SPS.

  6. Since SPS cannot automatically decide whether the incoming sessions are encrypted or not, it is required to setup another identical connection policy for the same sessions, for HTTPS. As a result, HTTP and HTTPS sessions will be saved into separate trails.

    1. Setup a new connection policy with the same settings as above.

    2. Set the Port to 443.

    3. Enable SSL encryption. For details, see Enabling SSL encryption in HTTP.

Enabling SPS to act as a HTTP proxy

Purpose:

To enable SPS to act as a HTTP proxy, perform the following steps.

Figure 159: HTTP Control > Connections — Act as HTTP proxy

Steps:
  1. Enable Act as HTTP proxy to configure the client to use SPS as a HTTP proxy.

  2. Select Inband destination selection as Target.

  3. To permit access to any HTTP servers, enter 0.0.0.0/0 into the Domain field. Alternatively, enter the IP address or subnet of the HTTP address you want permit access to. For IPv6 addresses, add ::/0 as well.

  4. To permit HTTP access to the destination servers on any port, leave the Domain > Port field empty. Otherwise, clients will be permitted only to access the specified port.

  5. Enter the port where SPS should accept HTTP connections into the To > Port field. The default port number when using the Act as HTTP proxy setting is 3128. This value should be the same as the proxy port setting on your clients.

  6. Ensure that you have set SPS as proxy on the clients.

Enabling SSL encryption in HTTP

Purpose:

To enable SSL encryption, perform the following steps. This setting either enforces SSL encryption, or accepts both HTTP and HTTPS requests.

Figure 160: HTTP Control > Connections> SSL Settings — Enabling SSL encryption in HTTP

Steps:
  1. In SSL Settings, select Permit HTTPS traffic. To control plain HTTP traffic with the same connection policy, enable Allow HTTP traffic.

  2. Select the certificate to show to the clients.

    • To use the same certificate for every session, select Use the same certificate for each connection.

      NOTE:

      When using the Use the same certificate for each connection option and the connection policy allows access to multiple servers using HTTPS, the client browsers will display a warning because the certificate used in the connection will be invalid: the Common Name of the certificate will not match the hostname or IP address of the server.

    • To use a separate certificate for every session, complete the following steps.

      1. Create a certificate authority that will be used to sign the certificates that SPS shows to the server. For details, see Signing certificates on-the-fly.

      2. Select Bridge certificate. In this case, SPS performs certificate bridging, that is, copies the data from the server's certificate into a new one, issued by the selected Certificate Authority.

        NOTE:

        Bridge certificate option does not work the same way as the Generate certificate on-the-fly option in other protocol settings.

      3. In the Signing CA field, select the certificate authority to use.

        NOTE:

        Import the certificate of the signing Certificate Authority to your clients. Otherwise, the client browsers will display a warning because of the unknown Certificate Authority.

  3. Select how SPS should authenticate the server.

    • To permit connections to servers without requesting a certificate, select No validation.

    • To permit connections only to servers having valid certificate that was signed by a specific CA, complete the following steps.

      1. Create a list of trusted Certificate Authorities that will be used to validate the certificates of the servers. For details on creating a trusted CA list, see Verifying certificates with Certificate Authorities.

      2. Select Only accept certificates authenticated by the trusted CA list.

      3. In the Trusted CA field, select the certificate authority list to use.

Configuring half-sided SSL encryption in HTTP

Purpose:

To enable half-sided SSL encryption, require HTTPS on client side, and HTTP on server side perform the following steps.

Figure 161: HTTP Control > Connections> SSL Settings — Enabling half-sided SSL encryption in HTTP

Limitations:

The Server Name Indication (SNI) extension of SSL and TLS is only supported by appropriate client OS and browser combinations. For details on the limitations, see Browsers with support for TLS server name indication. There are several unsupported scenarios, for example Windows XP + any version of Internet Explorer, Ubuntu Lucid + certain versions of Mozilla Firefox. When the client does not support SNI, the CN will contain the target IP, and the client browsers will display a warning when accessing these servers.

NOTE:

When Generate certificate on-the-fly is selected, and the connection is in transparent setup, the CN field is filled in using SNI (Server Name Indication). When the client does not support SNI, the CN will contain the target IP, which may cause certificate verification warning on the client browser.

Steps:
  1. In SSL Settings, select Require HTTPS on client side and HTTP on server side.

    NOTE:

    If the connection is configured at Target to Use fixed address and the port number is set to 443, SPS will still automatically use port 80 to connect to the server, when Require HTTPS on client side and HTTP on server side is selected.

  2. To use a fix certificate, select Use the same certificate for each connection and copy or upload the certificate.

    One Identity recommends using 2048-bit RSA keys (or stronger).

  3. To generate a certificate on-the-fly, signed by a provided Signing CA, select Generate certificate on-the-fly. It uses the parameters of the signing CA, excluding the CN field, which is filled with the name of the target host name.

    NOTE:

    When Generate certificate on-the-fly is selected, and the connection is in transparent setup, the CN field is filled in using SNI (Server Name Indication). When the client does not support SNI, the CN will contain the target IP, which may cause certificate verification warning on the client browser.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating