Identities aren’t stored when using an in-memory database

[pekspro]

• Create a new ASP.NET Core Web Application.
• Select ASP.NET Core 2.1, Web Application and change authentication to Individual User Accounts.

• In startup.cs replace:

  services.AddDbContext(options => options.UseSqlServer( Configuration.GetConnectionString("DefaultConnection")));

with

services.AddDbContext<ApplicationDbContext>(options =>
    options.UseInMemoryDatabase(Guid.NewGuid().ToString()));

Run the application and register an account. Logout and try to login with the created account. This will fail.

It looks like nothing is written in the Users-table when an account is registered.

I know there are some limitations when using an in-memory database, but shouldn’t this work? If it’s not supported I would prefer an exception than the current behavior.

[blowdart]

@HaoK

[HaoK]

I think this behavior might be by design, @ajcvickers can you confirm?

It appears that you need to use a static database name for it to work across requests:

            services.AddDbContext<ApplicationDbContext>(options =>
                options.UseInMemoryDatabase("identity"));

This works for me, but your new guid name didn't work for me either

[ajcvickers]

@HaoK Yep. The same database name needs to be used for saving and querying.

[pekspro]

😳 That so obvious! I don’t get how I could miss that. Thanks for the answer.