One Identity Safeguard for Privileged Sessions 7.5

When configuring HTTP or SSH connections, avoid using the IP address configured for administrator or user login on SPS.

The current version of SPS does not support the following features that are available for other protocols:
- Four-eyes authorization
Forwarding HTTP connections to an HTTP proxy is not supported. If your clients use an HTTP proxy to access the target servers, place SPS behind the proxy: Clients - HTTP Proxy - SPS.

Caution:
The Clients - SPS - HTTP Proxy scenario is not supported.
HTTP (and thus WebSocket) sessions cannot be terminated. They neither have a Terminate button on the SPS side, nor would be a termination request successful initiated from Desktop Player.

There is a related issue to remove the Terminate button from the SDP in case of HTTP / VNC over WebSocket sessions.

Authentication in HTTP and HTTPS

For the audited HTTP and HTTPS connections, One Identity Safeguard for Privileged Sessions (SPS) supports the following inband authentication methods for the HTTP protocol. These authentication methods are automatically supported for every Connection policy, without further configuration.

Basic Access Authentication (according to RFC2617)
The NTLM authentication method commonly used by Microsoft browsers, proxies, and servers

SPS records the username used in the authentication process into the Username and Remote username fields of the connection database.

For authenticated sessions, SPS can perform group-based user authorization that allows you to finetune access to your servers and services: you can set the required group membership in the Channel policy of the HTTP connection. Note that group-based authorization in HTTP works only for authenticated sessions (for HTTP/HTTPS connections, SPS uses this server only to retrieve the group membership of authenticated users, you cannot authenticate the users to LDAP from SPS). If a username is not available for the session, SPS will permit the connection even if the Remote groups field is set.

SPS does not store failed HTTP authentication attempts in the connection database. This means that the Verdict field of the Search page will never contain CONN-AUTH-FAIL values for HTTP connections.

Note that authentication also affects the way SPS handles HTTP sessions. For details, see Session-handling in HTTP.

Creating a new HTTP authentication policy

An authentication policy is a list of authentication methods that can be used in a connection. Connection definitions refer to an authentication policy to determine how the client can authenticate to One Identity Safeguard for Privileged Sessions (SPS).

To create a new authentication policy

Navigate to Traffic Controls > HTTP > Authentication Policies, and click .

Figure 195: Traffic Controls > HTTP > Authentication Policies — Configuring HTTP authentication policies
Enter a name for the policy into the Name field.
Select the authentication method used on the client-side in the Authenticate the client to SPS using field. For the client-side connection, SPS can authenticate the client inband (within the HTTP protocol) using the following authentication methods:
- LDAP: SPS will authenticate the client to the LDAP database set in the LDAP Server of the connection policy. To use LDAP authentication on the client side, select Authenticate the client to SPS using > LDAP.
  
  NOTE:SPS will authenticate the client-side connection to the LDAP server configured in the connection policy. This is not necessarily the same as the LDAP server used to authenticate the users accessing the SPS web interface.
- Local user database: Authenticate the client locally on the SPS gateway using a Local user database. Select the database to use in the Local user database field. For details on creating a Local User Database, see Creating a Local User Database.
- RADIUS: SPS will authenticate the client to the specified RADIUS server. Select Authenticate the client to SPS using > RADIUS, enter the IP address (use an IPv4 address) or hostname of the RADIUS server into the Address field, the port number of the RADIUS server into the Port field, and the shared secret of the RADIUS server into the Shared secret field. Only password-authentication is supported (including one-time passwords), challenge-response based authentication is not.
  
  To add more RADIUS servers, click and fill in the respective fields.
- None: Do not perform client-side authentication, the client will authenticate only on the target server.
Specify the time remaining until a successful gateway authentication times out into the Gateway Authentication Timeout field.

To avoid interruptions for active HTTP sessions, select the Sessions Extend Gateway Authentication checkbox. When enabled, active HTTP sessions can extend the gateway authentication beyond the configured timeout.
Click Commit.

NOTE: The client-side authentication settings apply for authenticating the user inband (that is, within the HTTP protocol) to the SPS gateway.

One Identity Safeguard for Privileged Sessions 7.5 - Administration Guide

Limitations in handling HTTP connections

Authentication in HTTP and HTTPS

Creating a new HTTP authentication policy

Setting up HTTP connections

Topics:

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

One Identity Safeguard for Privileged Sessions 7.5 - Administration Guide

Limitations in handling HTTP connections

Authentication in HTTP and HTTPS

Creating a new HTTP authentication policy

Setting up HTTP connections

Topics: