Active Directory or SQL server which way to go?
If i want to generate a menu structure depending on who is logged in
in an intranet system(using windows authentication) is it better to use the
GROUPS in Active Directory
or to move the Active Directory groups into a Sql Server database and base
the authrorization and authentication on the SQL Server roles/groups?
Whats the best way to make use of the GROUPS in active directory to
users apart from using web.config where you have to set it configuratively
like below(but i don't want this)
<allow roles="DOMAIN\HRUsers" />
<deny users="*" />
This works if i want to deny users who are not part of the GROUP
"HRUSERS"(Which just denies the URL .aspx page)
Is it possible to store/collect all the Active Directory groups and use it
in code to validate against USERS?
(Apart from storing it in SQL server?)
programmatically by doing :-
If Not (User.IsInRole("HR")) And Not (User.IsInRole("Managers")) Then
' Display the Button
' Don't display it!
The badside to these methods is that if you are calling a method several
times from different applications, you will need to repeat the logic all
the time. How can i do it declaratively using Active Directory.
I know if i use a database with stored procedures that would be a benefit.
By rperez in forum Database
Last Post: 01-02-2009, 04:14 PM
By alex in forum Database
Last Post: 11-03-2005, 05:27 AM
By Dan Staggs in forum Careers
Last Post: 08-07-2002, 11:04 AM
By Evan Schmitke in forum Database
Last Post: 01-21-2002, 02:31 PM
By Becky in forum Database
Last Post: 07-11-2000, 03:27 PM
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL