Sessions and Logout
Sessions are created (always) when a user signs on through PingOne and an existing session does not exist for the client.
-
A session is tied to all applications that the user signed into on that client (browser).
-
Sessions are identified through a session cookie when a user signs on (calls the authorize endpoint).
-
Sessions are associated with an entire SSO session, which includes all applications using the session.
-
A sign-off action terminates the entire SSO session and logs the user out of all applications using the session.
Session management use cases often call the following platform API resources:
| Platform API | Description |
|---|---|
The Sessions service enables you to manage sessions for either specified or unspecified (anonymous) users. Anonymous sessions are short-lived sessions that are created while the user authentication process occurs. |
|
These endpoints represent the user session associated with a flow. You can read all sessions, read a single session, or delete a single session associated with a user ID. |