HTTP settings determine the parameters of the connection on the protocol level, including timeout value, and so on.
Modifying timeout settings is recommended only to advanced users. Do not modify these settings unless you exactly know what you are doing.
To create a new HTTP settings profile or edit an existing one
Navigate to the Settings tab of the HTTP Control menu item and click to create a HTTP setting profile. Enter a name for the profile (for example http_special).
Figure 169: HTTP Control > Settings — Creating and editing protocol-level HTTP settings
Click to display the parameters of the profile.
Modify the parameters as needed. The following parameters are available:
Idle timeout: Timeout value for the session in seconds. To avoid early timeout, set it to a larger value, for example a week (604800 seconds).
Determining if a connection is idle is based on the network traffic generated by the connection, not the activity of the user. For example, if an application or the taskbar of a graphical desktop displays the time which is updated every minute, it generates network traffic every minute, negating the effects of timeout values greater than one minute and preventing One Identity Safeguard for Privileged Sessions (SPS) from closing the connection.
Session timeout: Timeout value for the session in seconds.
Enable pre channel check: Select this option to evaluate the connection and channel policies before establishing the server-side connection. That way if the connection is not permitted at all, SPS does not establish the server-side connection.
This option cannot be disabled.
To distinguish the audited HTTP requests and responses based on the session cookies of web applications, click Session Cookie Settings > , and enter the name of the session cookie, for example, PHPSESSID, JSESSIONID, or ASP.NET_SessionId. Note that the names of session cookies are case sensitive.
Repeat this step to add multiple cookie names. Note that if you list multiple cookie names, SPS will use the first one it finds to assign the requests to a session.
To configure TLS security settings on both the Client side and the Server side, proceed to TLS security settings.
Figure 170: <Protocol> Control > Settings > TLS security settings - configuring TLS security settings
Cipher strength specifies the cipher string OpenSSL will use. The following settings options are possible:
Recommended: this setting only uses ciphers with adequate security level.
Custom: this setting allows you to specify the list of ciphers you want to permit SPS to use in the connection. This setting is only recommended in order to ensure compatibility with older systems. For more details on customizing this list, check the 'openssl-ciphers' manual page on your SPS appliance.
For example: ALL:!aNULL:@STRENGTH
Minimum TLS version specifies the minimal TLS version SPS will offer during negotiation. The following settings options are possible:
TLS 1.2: this setting will only offer TLS version 1.2 during negotiation. This is the recommended setting.
TLS 1.1: this setting will offer TLS version 1.1 and later versions during negotiation.
TLS 1.0: this setting will offer TLS version 1.0 and later versions during negotiation.
Note that SPS only permits TLS-encrypted connections. SSLv3 is not supported.
Select this settings profile in the HTTP settings field of your connections.