title

OpenID Connect Back-channel Logout Security

This mechanism is server-to-server, making it more reliable than front-channel methods that depend on the user's browser. The IdP will directly notify each RP (Relying Party aka Service Provider) that a user's session has ended by sending a signed logout_token. The RP must validate this token and terminate the corresponding local session.

Key Benefits:

Higher reliability and security: Server-to-server logout does not rely on the user’s browser, reducing failures caused by network issues, blocked scripts, or closed sessions.
Consistent session termination: Signed logout_token notifications ensure each RP can securely validate and promptly terminate the correct local user session.

LPD-20764 - OpenID Connect Back-channel Logout (OP initiated SLO)

Using OpenID Connect

Generally Available (aka OOTB)

Automated Consent Renewal Security

GDPR (EU) requires consent renewal every 12 months. Some national data protection guidelines even recommend more frequent renewal, such as every 6 months.

We the renewal periods configurable where the administrator can manually add a number of months (maximum 12) to define the renewal period.

Key Benefits:

Supports regulatory compliance: Provides the technical capability to align consent renewal with GDPR and national data protection guidelines, including more frequent renewal requirements.

LPD-65277 - Automated Consent Renewal

Configuring the Consent Renewal Period

Generally Available (aka OOTB)