Skip to content

Update logout to endsession #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from
Open

Update logout to endsession #171

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5590e36
Update logout to endsession
ModMaker101 Jul 20, 2025
02e47d1
Update aspnet-core.md
ModMaker101 Jul 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 10 additions & 12 deletions integrations/aspnet-core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -304,34 +304,32 @@ that allows generating a unique `request_uri` and caching the received requests
an automatic redirection to the current page with the other parameters removed is triggered by OpenIddict and the token entry is redeemed
once the authorization or logout demand has been completed by the user.

To enable this feature, you need to use the dedicated `EnableAuthorizationRequestCaching()` and/or `EnableLogoutEndpointPassthrough()` APIs:
To enable this feature, you need to use the dedicated `EnableAuthorizationRequestCaching()` and/or `EnableEndSessionEndpointPassthrough()` APIs:

```csharp
services.AddOpenIddict()
.AddServer(options =>
{
options.EnableAuthorizationRequestCaching()
.EnableLogoutEndpointPassthrough();
.EnableEndSessionEndpointPassthrough();
});
```

### Authentication scheme forwarding <Badge type="warning" text="client" />

To simplify triggering authentication operations for a specific client registration, the OpenIddict client offers a built-in authentication scheme
forwarding feature that allows using the provider name assigned to a client registration as an authentication scheme in ASP.NET Core:

```csharp
app.MapGet("challenge", () => Results.Challenge(properties: null, authenticationSchemes: [Providers.GitHub]));
```
To simplify handling large authorization or end session process, the OpenIddict server ASP.NET Core integration includes a built-in feature
that allows generating a unique `request_uri` and caching the received requests in a request token persisted in OpenIddict's tokens table: when this feature is enabled,
an automatic redirection to the current page with the other parameters removed is triggered by OpenIddict and the token entry is redeemed
once the authorization or end session demand has been completed by the user.

This feature is enabled by default but can be disabled if necessary using `DisableAutomaticAuthenticationSchemeForwarding()`:
To enable this feature, you need to use the dedicated `EnableAuthorizationRequestCaching()` and/or `EnableEndSessionEndpointPassthrough()` APIs:

```csharp
services.AddOpenIddict()
.AddClient(options =>
.AddServer(options =>
{
options.UseAspNetCore()
.DisableAutomaticAuthenticationSchemeForwarding();
options.EnableAuthorizationRequestCaching()
.EnableEndSessionEndpointPassthrough();
});
```

Expand Down