---
title: OIDC authenticated sessions
description: Logging in to the OpenID provider and obtaining tokens are established processes in the OpenID specification; however, keeping the relying party informed of the session's validity is not as straightforward. The authenticated session in AM is unavailable to the relying party. The only information the relying party has is the expiration time of the ID token, which might be undesirable.
component: pingam
version: 8.1
page_id: pingam:am-oidc1:manage-sessions-openid-connect
canonical_url: https://docs.pingidentity.com/pingam/8.1/am-oidc1/manage-sessions-openid-connect.html
keywords: ["OpenID Connect (OIDC)", "Standards", "Authentication", "Sessions"]
page_aliases: ["oidc1-guide:manage-sessions-openid-connect.adoc"]
---

# OIDC authenticated sessions

Logging in to the OpenID provider and obtaining tokens are established processes in the OpenID specification; however, keeping the relying party informed of the session's validity is not as straightforward. The authenticated session in AM is unavailable to the relying party. The only information the relying party has is the expiration time of the ID token, which might be undesirable.

To solve this problem, AM supports the following OIDC specifications:

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

#### [OIDC 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]

#### [OIDC backchannel logout](backchannel-logout.html)

AM notifies relying parties when an authenticated session becomes invalid.