Last post May 26, 2016 09:09 AM by Nan Yu
May 25, 2016 03:13 PM|abnormallynormal|LINK
I'm building a new ASP.net 4.5 web forms application that needs to use an existing database schema to provide authentication & authorization. The user, role and group tables are part of a legacy application's database and I must use that security model.
Can someone lead me in the right direction? I can't find any documentation that discusses security when integrating with an existing database. I see plenty of examples for Active Directory and all the other option you might use if starting completely from
scratch. But I can't find anything that explains how to do security with an existing database.
I need to figure out how to
Do I need to create my own complete Membership Provider? That seems overkill for the simple tasks listed above that I need to accomplish. All user and security maintenance is handled in the legacy application.
May 26, 2016 09:09 AM|Nan Yu|LINK
Hi Bill Merkley,
Please refer to this thread :http://stackoverflow.com/questions/31096711
You can simply customize the standard membership UserProfile table like in these examples:
Or you could use your own existing data and map your users by ID or unique user name to the standard membership users. If you use this, keep in mind to keep it consistent (i.e. when handling users in your application).