This section describes the HTTP settings that determine the parameters of the connection on the protocol level, including timeout value, session cookies, and TLS settings.
|
|
Caution:
Modifying timeout settings is recommended only for advanced users. Do not modify these settings unless you exactly know what you are doing. |
To create a new HTTP setting profile or edit an existing one
-
Navigate to the Settings tab of the HTTP Control menu item.
-
Click
to display the parameters of a profile.
Figure 204: HTTP Control > Settings — Creating and editing protocol-level HTTP settings
-
To create a new HTTP setting, click Create new.
-
On Name and timeout, enter a name for the new profile and configure the timeout values. The following parameters are available:
-
Name: This is a required field. The name must be unique, and the accepted characters are the letters of the English alphabet (A-Z, and a-z) and the underscore (_) character.
-
Idle timeout: This is a required field. Timeout value for the session in seconds. The accepted values are positive integers. To avoid early timeout, set it to a larger value, for example a week (604800 seconds).
Caution: 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: This is a required field. Timeout value for the session in seconds. The accepted values are positive integers.
-
Error template: Use the error templates to send customized HTTP error messages to the users. The error templates, created on HTTP Control > Error templates, contain the following data:
-
Customizable HTTP error messages
-
Brand name
-
Color
-
(Optional) Logo
For more information, see Customizing HTTP error templates.
-
Figure 205: HTTP Control > Settings > Create a new HTTP setting - Name and timeout
-
-
Proceed to Session cookies.
To distinguish the audited HTTP requests and responses based on the session cookies of web applications, click Add cookie, 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.
Figure 206: HTTP Control > Settings > Create a new HTTP setting - Session cookies
-
To configure TLS security settings on both the Client side and the Server side, proceed to TLS security settings.
Figure 207: HTTP Control > Settings > Create a new HTTP setting - TLS settings
NOTE: Note that SPS only permits TLS-encrypted connections. SSLv3 is not supported.
-
Minimum TLS version specifies the minimum TLS version SPS offers during the negotiation. The following options are available:
-
TLS 1.2: this setting only offers TLS version 1.2 during the negotiation. This is the recommended setting.
-
TLS 1.1: this setting offers TLS version 1.1 and later versions during the negotiation.
-
TLS 1.0: this setting offers TLS version 1.0 and later versions during the negotiation.
-
-
Cipher strength specifies the cipher string for OpenSSL. The following options are available:
-
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 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
-
-
-
To create the new setting and to save it, click Create and after that, click Commit changes.
-
Select this profile in the HTTP settings field of your connections.
