Always resolve the registered token delivery mode (rejecting ping/push clients
when the mode is not enabled and push clients at the token endpoint), validate
client notification tokens against the RFC 6750 b64token syntax, restrict signed
requests to the advertised algorithms, share the notification endpoint check,
reject unauthenticated or oversized notifications before parsing, apply the
standard token response validation to pushed payloads and drop the Polly
dependency of OpenIddict.Server.SystemNetHttp.
Allow client registrations to send signed backchannel authentication requests,
cover successful ping redemption and push validation on the client and validate
a real server push payload with the OpenIddict client.
Convert session store failures to server_error responses (400) as required by OIDC Back-Channel Logout 1.0 section 2.8, validate that the back-channel and front-channel logout endpoints can terminate sessions in the ASP.NET Core and OWIN host options, require the exp claim by default (opt-out via DisableLogoutTokenExpirationRequirement, disabled for the BFF endpoint), bound future iat values by the clock skew, keep an atomic in-memory replay guard when a distributed cache is used, warn about mismatched frontchannel_logout_session_required settings and reuse SecurityEventTypes.BackchannelLogout in the BFF.
Only invoke session stores for front-channel logout requests verified against the local session (opt-out via DisableFrontchannelLogoutSessionVerification), honor FrontchannelLogoutSessionRequired, select registrations sharing an issuer using the logout URIs, release logout token identifiers when back-channel logout handling fails, enforce nbf, support encrypted logout tokens and use dedicated issuer mismatch errors.
- POST-only logout_token extraction, JSON error responses and no-store headers for back-channel logout
- Front-channel logout: sign-out of the matching local session (sid/registration/issuer) using a configured scheme/authentication type, no-cache headers
- Pass-through modes for both endpoints; logout token principal and session_state exposed in authentication properties
- ASP.NET Core integration tests
- Delegate OpenIddictClientAspNetCoreBffLogoutTokenValidator to AuthenticateWithLogoutTokenAsync
- Allow overriding the logout token maximum age per authentication demand
- Reuse a cached dynamic registration only if issuer, provider name and client id are unchanged
- Check the cache before creating configuration managers/DPoP keys
- Purge expired cache entries on insert
- Tests for changed and unchanged cached registrations; plan updated
- Add IOpenIddictClientRegistrationProvider (static options provider registered by default, AddRegistrationProvider)
- Extract registration initialization/validation from OpenIddictClientConfiguration
- OpenIddictClientService resolves static and dynamic registrations; dynamic ones are validated (declared redirect URIs, no static id collision) and cached by id (DynamicRegistrationCacheLifetime)
- Handlers default to the unique registration through the service
- ASP.NET Core: decorate IAuthenticationSchemeProvider to resolve dynamic provider names as forwarded schemes
- OWIN: resolve dynamic provider names for forwarded challenges, sign-outs and authentication
- WebIntegration: make ConfigureProvider/ValidateProvider browsable for dynamic registrations
- EnableDPoPTokenBinding(); per-registration DPoPSigningCredentials (ephemeral P-256 by default)
- Negotiate DPoP from dpop_signing_alg_values_supported; send proofs to token, PAR and userinfo (DPoP scheme + ath)
- Retry once on use_dpop_nonce and cache server nonces per authority
- OpenIddictClientService.CreateDPoPProofAsync/GetDPoPJsonWebKeyThumbprint for resource calls
- System.Net.Http handlers attach DPoP header and extract DPoP-Nonce
- Validate DPoP proofs at the token, PAR and userinfo endpoints (typ, alg, public jwk, htm/htu, iat, ath)
- Replay protection via redeemed token entries when token storage is enabled
- Optional server nonces (use_dpop_nonce + DPoP-Nonce header)
- Bind access tokens and public-client refresh tokens with cnf.jkt; token_type=DPoP
- dpop_jkt at authorization/PAR, enforced at code redemption
- Global RequireDPoP option, per-client ft:dpop requirement, discovery metadata
- DPoP scheme and WWW-Authenticate algs in ASP.NET Core and OWIN hosts
Server: opt-in request object support (EnableRequestObjectSupport) for the authorization
and pushed authorization endpoints, request objects validated using the client JSON Web Key
Set (optionally encrypted), RFC 9101 merge semantics, global and per-client requirements
(RequireSignedRequestObjects, ft:jar) and discovery metadata.
Client: request objects sent when required by the server or enabled in the registration
(UseSignedRequestObjects), signed with the registration's asymmetric key.