The following tables list the cookies used in Dynatrace web UI. Due to self-monitoring, RUM cookies are also added. All listed cookies are first-party cookies.
The table below contains cookies placed in the Dynatrace web UI for single sign-on (SSO). Depending on the infrastructure provider used, Dynatrace might place additional cookies, for example, AWSALB and AWSALBCORS.
| Cookie | Expires | Purpose |
|---|---|---|
| Session | Indicates if a user is logged in or not. |
| Session | Serves as cross-site request forgery (CSRF) protection when moving between servlets in SSO. |
| 5 years | Contains a unique Base32 identifier that indicates to SSO that a user is logging in from a new device. The identifier is created based on the user login, browser, and user agent. |
| Session | Stores the OpenID |
| Session | Stores the OpenID |
| Session | Stores |
| Session | Contains an SHA-256 hash of a random UUID. When a user signs in via OpenID, this cookie is used to track the session state via the SSO OpenID iFrame and perform frontend logout if necessary. |
| 3 months | Added when a user selects the Remember me option to store their credentials. Thanks to this option, the user doesn't have to provide their credentials again when the session expires, and the user is logged in automatically. |
| 5 minutes | Prevents the user from becoming stuck following a failed federated login if the user selected the Remember me option to store their credentials. If the user is signed in, this cookie is deleted. |
| Cookie | Expires | Purpose |
|---|---|---|
| 1 hour | Load balancer (HA Proxy) session stickiness. |
| Session | Web server session cookie. |