Get Live Help
The following sections describe configuration settings available only for the HTTP protocol. Use the following policies to control who, when, and how can access the HTTP connection. For details on configuring Channel Policies, see Creating and editing channel policies. For a list of supported client applications, see Supported protocols and client applications.
Auditing HTTP and HTTPS connections is possible in both transparent and non-transparent modes. SPS can also be used as an HTTP/HTTPS proxy to simplify client configuration and integration into your network environment, or it can forward HTTP traffic, behaving as a HTTP tunnel.
Channel Policy: The HTTP protocol has only one channel type with no special configuration options. The available channel policy options are the following: From, Target, Time policy, Record audit trail, and Remote groups. Note that the Remote groups option is used only if the user performs inband authentication using one of the supported HTTP authentication methods (see Authentication in HTTP and HTTPS). To retrieve the groups of an authenticated user from an LDAP database, you must also set an LDAP Server in the Connection Policy (for HTTP/HTTPS connections, One Identity Safeguard for Privileged Sessions (SPS) uses this server only to retrieve the group membership of authenticated users, you cannot authenticate the users to LDAP from SPS). For details on configuring these options, see Creating and editing channel policies.
When setting Target, note the following:
If the connection uses DNAT (NAT destination address), the target address of the original client will be compared to the Target parameter of the Channel policy, that is not necessarily equivalent with the server's address.
If the connection is redirected to a Fix address, the redirected address will be compared to the Target parameter of the Channel policy.
HTTP connections: For details, see Setting up HTTP connections.
HTTP sessions: HTTP settings determine the parameters of the connection on the protocol level, including timeout value, and so on. For details, see Session-handling in HTTP.
HTTP settings: HTTP settings determine the parameters of the connection on the protocol level, including timeout value, and so on. For details, see Creating and editing protocol-level HTTP settings.
Avoid using the IP address configured for administrator or user login on One Identity Safeguard for Privileged Sessions (SPS) when configuring HTTP or SSH connections.
The current version of SPS does not support the following features that are available for other protocols:
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.
The Clients - SPS - HTTP Proxy scenario is NOT supported.
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.
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 HTTP Control > Authentication Policies, and click .
Figure 163: HTTP Control > 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.
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.
The client-side authentication settings apply for authenticating the user inband (that is, within the HTTP protocol) to the SPS gateway.