asking info form ASP.NET 2.0 to Windows Active Directory

[Lucky]

hi guys,
after long long efforts i got access to the active directory for
"Intigrated windows authentication". now i', suppose to get access the
network resources.

the problem is i'm getting access to the active directory but when i
search for some users into the active directory, it returns none though
there are more then 42 users exists.

the code has been tested with Desktop Application locally. it is
working fine for retriveing data. but when i used "intigrated windows
authentication" and allowe server for "trusted for deligation", i'm not
able to retrive any users list anymore.

the code is :

entry = new
System.DirectoryServices.DirectoryEntry("LDAP://" + Settings.Domain);
mySearcher = new
System.DirectoryServices.DirectorySearcher(entry);
mySearcher.Filter = ("(objectClass=user)");
writer.WriteLine("FindNoExistingUserInPowerLearn : " +
entry.ToString());
writer.WriteLine("Entry : " +
entry.AuthenticationType.ToString());
writer.WriteLine("Entry : " +
entry.Options.SecurityMasks.ToString());
writer.WriteLine("Entry : " +
entry.Properties.Count.ToString());
System.DirectoryServices.SearchResultCollection results =
mySearcher.FindAll();
writer.WriteLine("Result Found : " +
results.Count.ToString());

i've some doubt that. the aspnet a/c used by the aspnet_wp.exe can only
authenticate the users against active directory but can't fetch users
information from the active directory.

if someone has any exp. with such situation, please share with me.

thanks,
Lucky

 

[Guest]

i've some doubt that. the aspnet a/c used by the aspnet_wp.exe can only

authenticate the users against active directory but can't fetch users
information from the active directory.

Hello,
If you are using integrated windows authentication for your web app, and it
won't cause a security risk to your app, then try turning impersonation on in
your web.config file.

Either that or set impersonation on in the web.config file and get it to run
as a fixed low privilege account that exists in the active directory.

As mentioned though, you'll have to make sure this doesn't cause a security
risk.