CSLA .NET discussion

Re: Security Database

Stefanus — Fri, 15 Jun 2012 16:57:53 GMT

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 :)

JonnyBee — Thu, 14 Jun 2012 14:08:49 GMT

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.

Tiago Freitas Leal — Thu, 14 Jun 2012 06:43:34 GMT

Hi Stefanus,

There are some reasons I can think of:

use integrated authentication on some scenarios and just don't use the security datanase
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)
use the same security database for several different applications

Regards

Stefanus — Thu, 14 Jun 2012 03:05:25 GMT

Hi all...

I've read csla books, and i want to ask about :

Why do rocky make suggest two database ( one for app ) and one for security database ?

Is there any explanation for this ?? reasons ?

thanks a lot