Session cookies in Identity Authentication are protected with a Transport Layer Security (TLS) and with the Secure and HttpOnly attributes. You don't need to make any additional configurations for Identity Authentication.
Authentication Session Trackin
Cookie |
Path |
Expiration |
Protection |
Value |
Info |
Reference |
---|---|---|---|---|---|---|
|
/ |
Session |
|
secure random token |
Track the authentication session of the user at the identity provider. The cookie is sent to the browser so the users can sign in to the application without the need to provide their credentials every time they access it. |
|
|
/ |
3 months |
|
secure random token |
Allow user to keep their session for an extended period of time even after closing the Web browser |
Authentication & Single Sign-On Screens
Cookie |
Path |
Expiration |
Protection |
Value |
Info |
Purpose |
---|---|---|---|---|---|---|
|
/ |
Session |
|
|
|
|
|
/ |
Session |
|
|
|
|
`` |
/ |
Session |
|
|
|
|
`` |
/ |
Session |
|
|
|
|
Cookie |
Description |
Default Validity |
|
Reference |
---|---|---|---|---|
Remember Me |
The cookie is sent to the browser so the users can sign in to the application without the need to provide their credentials every time they access it. |
3 months |
|
|
Conditional Authentication |
Identity Authentication stores the user identifier in a persistent cookie in the browser. |
36 months |
|
|
Locale |
If the locale is set, the emails use the language set there, if there is a template in that language. If there is no template in that language, the emails use the English language template. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Related Information
Configure the Remember Me Option
Configure Conditional Authentication for an Application
Add Logon Overlays in Customer Applications