Authentication Settings
Use the Authentication Settings page to configure whether the browser retains the session token (ST) cookie after it closes.
Configuring cookie persistence
Use the Cookie Setting section to configure ST cookie persistence:
- Persistent cookie (default)
-
The browser retains the ST cookie after it closes until the cookie expires or is manually removed.
- Non-persistent cookie
-
The browser discards the ST cookie when it closes. Non-persistent cookies are useful for kiosk or shared workstation use cases when you don’t want the browser to retain the ST cookie after it closes.
Without a persistent ST cookie, the following might not work as intended after the user closes or restarts their browser:
-
Long-lived sessions in PingOne DaVinci flows
-
Authentication policy conditions, such as Last sign-on older than
-
PingID policies that rely on device or recent-authentication context
The ST cookie is also unavailable if the user switches browsers, uses a private or incognito window, or clears cookies.
-
Before you begin
You must have the Environment Admin role or a custom role with equivalent permissions to view or update single sign-on (SSO) cookie settings.
Steps
-
In the PingOne admin console, go to Authentication > Authentication Settings.
-
In the Cookie Setting section, click the Pencil icon ().
-
For Browser-Persistent Session-Token Cookie, set the desired ST cookie persistence behavior:
-
Enabled (default): PingOne uses a persistent ST cookie to track session information. The browser retains the cookie after it closes until the cookie expires or is manually removed.
-
Disabled: PingOne uses a non-persistent ST cookie. The browser discards the cookie when it closes. When a user closes or restarts their browser, session and other state information is lost.
When you update this setting, PingOne records an SSO cookie settings updated event in the Audit log. Learn more in Running an audit report.
-
-
Click Save.