ApiAuthorizationDbContext<TUser> force TUser to extends IdentityUser instead of IdentityUser<TKey>

Describe the bug

At the moment, ApiAuthorizationDbContext<TUser> force TUser to extends IdentityUser instead of IdentityUser<TKey>. This means it is impossible to use Identity Server on application with ApplicationUser : IdentityUser<Guid> (or anything different from IdentityUser<string>)

To Reproduce

Steps to reproduce the behavior:

1. Using ASP.NET Core 3.0 Preview 4
2. Create a new React or Angular template with Identity
3. Change ApplicationUser to extends IdentityUser<Guid> instead of IdentityUser
4. Get error: Error CS0311 The type 'WebApplication.Models.ApplicationUser' cannot be used as type parameter 'TUser' in the generic type or method 'ApiAuthorizationDbContext<TUser>'. There is no implicit reference conversion from 'WebApplication.Models.ApplicationUser' to 'Microsoft.AspNetCore.Identity.IdentityUser'.

Expected behavior

I would expect ApiAuthorizationDbContext to accept another generic to indicate the key type (e.g. ApiAuthorizationDbContext<ApplicationUser, Guid>)

[cherchyk]

2020 Looks like it was not fixed yet…

Am I wrong?

[ajcvickers]

Re-opening, since ApiAuthorizationDbContext doesn’t follow best practices for a DbContext shipped for others to use. In particular:

• It should expose a public constructor that takes a generic DbContextOptions<TContext>. Otherwise people resolving this directly will have issues when multiple contexts are registered in D.I.
• It should expose a protected constructor that takes a non-generic DbContextOptions for use when other classes inherit from it.