Security Database

Reply

Tiago Freitas Leal replied on Thu, Jun 14 2012 1:43 AM

rated by 0 users

Hi Stefanus,

There are some reasons I can think of:

1. use integrated authentication on some scenarios and just don't use the security datanase
2. use the same security database for two or more instances of the same application (different departments, but IT board member must have access to all of them)
3. use the same security database for several different applications

Regards

Reply

JonnyBee replied on Thu, Jun 14 2012 9:08 AM

rated by 0 users

Historically Security has often been separated from the actual database.

In the early 2000's we had Active Directory Application Mode (ADAM) that later became Active Directory Lightweight Directory Service (AD LDS).

Today we still have ASP.NET Membership Provider, http://msdn.microsoft.com/en-us/library/yh26yfzy.aspx and the WebMatrix WebSecurity that wraps a membership provider.

The ProjectTracker sample uses the membership provider for users and roles.

Reply

Stefanus replied on Fri, Jun 15 2012 11:57 AM

rated by 0 users

Hi Jonny and Tiago..

Thanks a lot for your quick reponse..

@Jonny, honestly I have not learn / try / read about what you said..

    but i will try to look for that later.. :) thanks

@ tiago, thanks for sharing your opinion :)