BFF - Resolve IUserSessionStore in BffServerAuthenticationStateProvider using scoped service container #2251
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working with server-side session management using Entity Framework Core, an error is always visible in the logs:
Steps to reproduce
.AddServerSideSessions() // Add in-memory implementation of server side sessions
.AddBlazorServer();
.AddEntityFrameworkServerSideSessions(options =>
{
options.UseSqlite("Data Source=database.dat", p => p.MigrationsAssembly("BlazorBffApp"));
})
.AddBlazorServer();
Observations
When debugging the issue, it seems
BffServerAuthenticationStateProvidertries to accessIUserSessionStorewhich has an already disposedSessionDbContext.The reason is that Blazor's
RevalidatingServerAuthenticationStateProvider.RevalidationLoophas a task delay during which the Blazor component goes out of scope, and disposes most of its dependencies, including the DbContext.In this PR, the responsibility for creating/disposing a DI scope is moved to
BffServerAuthenticationStateProviderto prevent the database IUserSessionStore and its dependencies from being disposed when authentication state is revalidated asynchronously.