Re: ActiveDirectoryMembershipProvider & ValidateUser
- From: "Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 27 Feb 2007 13:40:32 -0600
I doubt that anything in AD needs to change. My guess is that my lack of
detailed knowledge of how the membership provider is designed is the problem
here.
A few more questions:
- Is the AD in question a single domain forest or are there multiple
domains involved?
- If multiple domains, is the user you are trying to authenticate in a
different domain than what you've configured the provider to access?
I'll try to do some poking around this afternoon to see if I can figure out
what the likely cause of the problem is.
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:6342FA3D-605A-4F95-A93A-1875EC97D6B1@xxxxxxxxxxxxxxxx
I just tried your suggestion and it still fails.
Could this have anything to do with the way the Active Directory itself is
configured? If so, what information do I need to ask our support guys for?
"Joe Kaplan" wrote:
What happens if you change:
attributeMapUsername="sAMAccountName"
to:
attributeMapUsername="userPrincipalName"
And then try the user@domain format?
.
- References:
- Re: ActiveDirectoryMembershipProvider & ValidateUser
- From: Joe Kaplan
- Re: ActiveDirectoryMembershipProvider & ValidateUser
- Prev by Date: error of configuration section handler for system.web/authorizatio
- Next by Date: Re: CAS newbie
- Previous by thread: Re: ActiveDirectoryMembershipProvider & ValidateUser
- Next by thread: Re: ActiveDirectoryMembershipProvider & ValidateUser
- Index(es):
Relevant Pages
|