---
title: OpenID Connect user sessions
description: Logging in to the OpenID provider and obtaining tokens are well-stabilized processes in the OpenID specification. However, keeping the relying party informed of the session's validity is not as straightforward. The end user's session in AM is unavailable to the relying party, and therefore, the only information the relying party has is the expiration time of the ID token, which may be undesirable.
component: pingam
version: 7.2
page_id: pingam:oidc1-guide:manage-sessions-openid-connect
canonical_url: https://docs.pingidentity.com/pingam/8.1/am-oidc1/manage-sessions-openid-connect.html
llms_txt: https://docs.pingidentity.com/pingam/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
superseded_by: https://docs.pingidentity.com/pingam/8.1/am-oidc1/manage-sessions-openid-connect.html
---

# OpenID Connect user sessions

Logging in to the OpenID provider and obtaining tokens are well-stabilized processes in the OpenID specification. However, keeping the relying party informed of the session's validity is not as straightforward. The end user's session in AM is unavailable to the relying party, and therefore, the only information the relying party has is the expiration time of the ID token, which may be undesirable.

To solve this problem, AM supports different OpenID Connect specifications:

[icon: handshake, set=fad, size=3x]

#### [OpenID Connect session management](session-management.html)

Relying parties can request session information from AM, and act on it.

[icon: sign-out-alt, set=fad, size=3x]

#### [OpenID Connect backchannel logout](backchannel-logout.html)

AM notifies relying parties when a user session becomes invalid.