Re: WindowsTokenRoleProvider & Domain Groups

Are those domain local groups that are local to the domain the web server is
in? If the web server is in a different domain than the DLGs, then that is
the expected behavior.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Craig Wagner" <MSDNNospam207@xxxxxxxxxxxxx> wrote in message
news:958C765D-BF5D-4D62-BE3D-8416A0081B5A@xxxxxxxxxxxxxxxx
I've been researching using Domain Groups within our application. I found
a
code sample that I've been experimenting with, but need confirmation on
one
behavioral thing that I've noticed.

My web.config contains the following:

<system.web>
<authentication mode="Windows" />
<roleManager enabled="true"
defaultProvider="AspNetWindowsTokenRoleProvider" />
</system.web>

The IIS vdir has anonymous access turned off and Integrated Windows
Authentication turned on.

In my web page, I execute:

string[] members = Roles.GetRolesForUser();

The returned members include domain global groups and builtin groups. The
list does not include Domain Local groups to which I belong.

Is this expected behavior (the lack of domain local groups) or am I doing
something incorrectly?


.