Right AdminUsersFeature only works for ServiceStack Auth. Likewise all related classes like IAuthRepository and OrmLiteAuthRepository etc are only for ServiceStack Auth.
AdminUsersFeature only supports ServiceStack Auth, an entire new implementation would be needed for managing ASP .NET Identity Users.
We’ll eventually want to add Admin Users functionality to manage ASP .NET Core Users although still not sure what the best approach is, i.e. whether to include it in the templates, build it within Admin UI, try to update users table directly, try to use new Identity Auth APIs, etc. Will require a bit of R&D to determine what the best approach would be.
But when I click on the View All Database Tables, it wants me to log in again, but this time the login errors out saying:
which coincides with a 401 on the auth route.
When I compare to a clean template I notice the secondary login works (however it doesn’t ask for my 2FA), and if I navigate away and come back I need to authenticate again, but I get the 200 on the Authenticate.
@Charles If you delete the Auth.razor file in MyApp.Client/Pages it should fix it. I believe the /auth route was interfering with the login process for the admin.
I’ve updated the template with this fix so x new blazor-wasm MyApp will work as well, but you might need to run x --clear first.