Using the old aspnet membership with aspnet vNext

Question

UPDATE November 20, 2015

How can I authenticate against a database that have the users stored using the Old Membership Provider ? (the aspnet_* tables) Knowing that this database is used by other applications, so I don't have the option to migrate (or change) the database ?

For whom looking for migration look at Maxime Rouiller's answer

Old Question

Can I use the aspnet Membership with aspnet vNext ?,

• In my situation I can't migrate the old database, because I am building a new app/ui interface for an existing one based on the old Membership provider
• It will be a good idea if I can write some code to login without using the old Membership
• What needed exactly is to just validate the user against the hashed password, (no registration, no forgot password, etc ...)
• I prefer to not rely on the .net 4.x, and using the core50 (if available) instead (since I am planing to host it on linux later)

Answer 1

No. The old membership was dependent on the web.config being present and also was heavily dependent on the System.Web lifetime.

You are looking for a migration from your old membership to the new Identity 3.

The database should be easily portable. If you are planning to have it hosted on Linux, I would go as far as remove the dnx451 dependency altogether and just keep dnxcore50.

Tutorials:

• http://www.asp.net/identity/overview/migrations/migrating-an-existing-website-from-sql-membership-to-aspnet-identity
• http://travis.io/blog/2015/03/24/migrate-from-aspnet-membership-to-aspnet-identity/