Change the database in which ASP.NET Identity stores user data

We have created a new ASP.NET 4.5.1 project as follows:

Visual Studio 2013
New Project
Visual C#
Web
ASP.NET Web Application
Web API
Change Authentication
Individual User Accounts
Okay > Okay

In the solution explorer > App_Start > Startup.Auth.cs file there is the following code which configures ASP.NET Indentity. How do we change the database in which the UserManager stores user data?

static Startup()
{
    PublicClientId = "self";

    UserManagerFactory = () => new UserManager<IdentityUser>(new UserStore<IdentityUser>());

    OAuthOptions = new OAuthAuthorizationServerOptions
    {
        TokenEndpointPath = new PathString("/Token"),
        Provider = new ApplicationOAuthProvider(PublicClientId, UserManagerFactory),
        AuthorizeEndpointPath = new PathString("/api/Account/ExternalLogin"),
        AccessTokenExpireTimeSpan = TimeSpan.FromDays(14),
        AllowInsecureHttp = true
    };
}

Contents hide

Answers:

Method 1

Method 2

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

Additionally to what @ta.speot.is and @Shaun mentioned: You can also pass the name of the connection string (stored in the web.config) in your context to the base constructor of the IdentityDbContext

public class MyDbContext : IdentityDbContext<MyUser>
{
  public MyDbContext()
    : base("TheNameOfTheConnectionString")
  {
  }
}

This tutorial contains an extensive example.

Another way would be to use the name of the connection string as a parameter of your context constructor and pass it to the base constructor.

Method 2

Pass your own DbContext to the UserStore constructor or change the Web.config connection string named DefaultConnection. Either way the comments by @ta.speot.is are correct.

Correct

// do this - it's the factory pattern
UserManagerFactory 
= () => new UserManager<IdentityUser>(new UserStore<IdentityUser>(new MyDbContext()));

Incorrect

// do NOT do this - use the preceding code. 
var userStore = new UserStore<IdentityUser>(new MyDbContext());                       
var userManager = new UserManager<IdentityUser>(userStore);
UserManagerFactory = () => userManager;

Details

The UserStore class exposes a very basic user management api. In code, we configure it to store user data as type IdentityUser in the MyDbContext data store.

The UserManager class exposes a higher level user management api that automatically saves changes to the UserStore. In code, we configure it to use the UserStore that we just created.

The UserManagerFactory should implement the factory pattern in order to get one instance of UserManager per request for the application. Otherwise you will get the following exception:

The context cannot be used while the model is
being created. This exception may be thrown if the context is used
inside the OnModelCreating method or if the same context instance is
accessed by multiple threads concurrently. Note that instance members
of DbContext and related classes are not guaranteed to be thread
safe.

That’s all.

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes

Article Rating