openiddict/openiddict-core 7.0.0-preview.3 on GitHub

This release introduces the following changes:

As a preliminary step to the introduction of OAuth 2.0 Token Exchange support in a future 7.0 preview, the entire OpenIddict code base was updated to use new URI-style token type identifiers to represent token types (e.g urn:ietf:params:oauth:token-type:access_token). These new identifiers will replace the token_type_hint-inspired constants that previous versions of OpenIddict were using in the core, client, server and validation stacks. For more information, read #2296.

Note

While internally massive, this change should be completely transparent for most OpenIddict users. Only advanced users who implement custom handlers for the GenerateToken/ValidateToken events or use the ClaimsPrincipal.GetTokenType()/ClaimsPrincipal.SetTokenType() extensions will need to update their code to use the new values.

The Discord provider was updated to use the /users/@me endpoint instead of /oauth2/@me, which improves how userinfo claims are represented and returned to the application code (thanks @egans146 for suggesting this improvement! ❤️).

Important

This behavior change is breaking: developers are encouraged to review their Discord integration to determine whether their code should be updated to support the new claims representation.

New ClaimsPrincipal.AddClaim()/ClaimsPrincipal.AddClaims()/ClaimsPrincipal.SetClaim()/ClaimsPrincipal.SetClaims() overloads accepting System.Text.Json.Nodes.JsonNode instances have been added to make working with types derived from JsonNode easier.
An event identifier is now attached to all the logs generated by the OpenIddict core, client, server and validation stacks.
A few properties in OpenIddictClientModels didn't have an init constraint and have been fixed in 7.0.0-preview.3.

Tip

Note: this preview also includes all the changes introduced in the OpenIddict 6.3.0 release.