CODEWITHSUNDEEP
asp.netasp.net-coreasp.net-membershipasp.net-identity-2asp.net-identity-3
SJDoodle
SJDoodle

Reputation: 367

.Net Identity 2 vs 3

I understand .NET Identity, but lots of articles are coming up about Identity 2 and Identity 3. The latter (Identity 3) seems to only work for .NET Core solutions. So was thinking of using Identity 2. But I'm not clear:

Upvotes: 5

Views: 2140

Answers (2)

Adrian
Adrian

Reputation: 665

You can use identity 2 in Asp.Net Core and mantain the passwordhash in the database. Just add this code in startup.cs

 services.Configure<PasswordHasherOptions>(options => {
          options.CompatibilityMode = PasswordHasherCompatibilityMode.IdentityV2;
      });

Upvotes: 1

trailmax
trailmax

Reputation: 35106

Your choice is simple. If you build MVC5 application you can only use Identity 2. If you are building ASP.Net Core application you can only use Identity 3.

Identity 2 is in support, but not in active development. I.e. bugs will be fixed, but no new features will be provided.

If you are starting a new project, then I don't see a reason to use MVC5. All green-field projects should be done in ASP.Net Core with Identity 3

Upvotes: 3

Related Questions