Last post Jan 25, 2012 02:01 AM by raringsunny
Dec 21, 2011 05:48 PM|raringsunny|LINK
I am currently working on a project wherein we need to authorize a user using the Active Directory. The domain admin has created an AD Security group against which I need to authorize the Windows domain user.
The Security group has been created under the same domain e.g. domain name is "dom" and the user part of this domain is "john".
Now John has been added to the Security group "Accounting".
After reading about Authorization is that we can perform Authorization using the following stores.
If we are using the Active Directory, is "AuthorizationStoreRoleProvider" only object out of the three afore-mentioned role providers that I should be using to authorize a user?
I tried using WindowsTokenRoleProvider and it seems to work.
I used the following code to Authorize a user and it does recognize which user is added to the newly created Security Group in AD Server.
WindowsTokenRoleProvider objRP = new WindowsTokenRoleProvider();
Please confirm my understanding on the following points.
1) Can WindowsTokenRoleProvider object be used where we are using Active Directory for Security Groups or should it be used only on standalone systems where Windows users are created locally on the server
where website is hosted?
2) If I have Active Directory where the Security Group has been created, should I be using AuthorizationStoreRoleProvider instead?
Jan 25, 2012 02:01 AM|raringsunny|LINK
I was able to resolve this issue by simply using the fully qualified domain name along with the security group name.