Skip to content

Update the 6.0 -> 7.0 migration guide to include a note about DI resolution of custom manager types #177

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

Merged
kevinchalet merged 1 commit into from
Aug 18, 2025
Merged

Update the 6.0 -> 7.0 migration guide to include a note about DI resolution of custom manager types #177

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 7 additions & 3 deletions guides/migration/60-to-70.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,7 @@ that do not use the new `client-authentication+jwt` JSON Web Token type.

OpenIddict 7.0 no longer allows dynamically overriding the `prompt` value when using OAuth 2.0 Pushed Authorization Requests as the logic
internally used to support this scenario was too fragile and was removed. To prevent `login endpoint -> authorization endpoint` loops,
developers are now encouraged use `TempData` to store a flag indicating whether the user has already been offered to re-authenticate
developers are now encouraged to use `TempData` to store a flag indicating whether the user has already been offered to re-authenticate
and avoid triggering a new authentication challenge in that case. Here's an example:

```csharp
Expand Down Expand Up @@ -266,7 +266,11 @@ public sealed class CustomTokenManager<TToken> : OpenIddictTokenManager<TToken>
> The managers/stores service registration APIs present in `OpenIddictCoreBuilder` have also been reworked
> to make them trimming and Native AOT-compatible, which may require making a few changes to your code.
>
> See https://github.com/openiddict/openiddict-core/releases/tag/7.0.0-preview.2 for more information
> See https://github.com/openiddict/openiddict-core/releases/tag/7.0.0-preview.2 for more information.

> [!NOTE]
> If you use custom application/authorization/scope/token managers and expect the custom manager types to be resolvable via DI,
> read https://github.com/openiddict/openiddict-core/issues/2369 to learn more about a related change introduced in 7.0.

## Update your custom EF Core stores to use the new `IOpenIddictEntityFrameworkContext` and `IOpenIddictEntityFrameworkCoreContext` interface (if applicable)

Expand Down Expand Up @@ -404,7 +408,7 @@ review their Discord integration to determine whether their code should be updat

## Register your Entity Framework 6.x `DbContext` in the dependency injection container (if applicable)

In previous OpenIddict versions, the `OpenIddictEntityFrameworkBuilder.UseDbContext<TContext>()` automatically registered the `TContext`
In previous OpenIddict versions, the `OpenIddictEntityFrameworkBuilder.UseDbContext<TContext>()` API automatically registered the `TContext`
type in the dependency injection container as a scoped service if no pre-existing service descriptor for that type could be found.
While convenient, this behavior was inconsistent with the Entity Framework Core stores and was a hard-to-discover mechanism.

Expand Down
Loading