Re: User objects cannot be created in the specified container
- From: chand <chandmk@xxxxxxxxx>
- Date: Sun, 22 Jul 2007 04:55:51 -0700
Hi Joe,
Thank you for replying. Yes. CN is a group object. This CN has a list
of members that are allowed to access my application. This
configuration is identical to other CNs used by other applications
like "Business Objects" in the organization.
Root --> OU1--> OU12--> CN (group)
1. If I point the connection to Root, every thing works fine. But this
would allow every one in the organization to access my application.
The goal is to restrict access to a group of users
2. If I point the LDAP connection to OU12, I am not getting the above
error. However provider's 'ValidateUser' method is returning false for
any member in the CN group. Either this method is not searching the
group or not finding the users in the group. I am using
sAMAccountName attribute.
3. If we put a test user directly under OU12 every thing works. Is
this the only way to configure AD to work with
ActiveDirectoyMembershipProvider? Using the groups under OUs seems to
be the reasonable option as this allows the admin to manage users
without worrying about different applications.
Thank you,
chand
.
- Follow-Ups:
- Re: User objects cannot be created in the specified container
- From: Joe Kaplan
- Re: User objects cannot be created in the specified container
- References:
- User objects cannot be created in the specified container
- From: chand
- Re: User objects cannot be created in the specified container
- From: Joe Kaplan
- User objects cannot be created in the specified container
- Prev by Date: Re: User objects cannot be created in the specified container
- Next by Date: Re: User objects cannot be created in the specified container
- Previous by thread: Re: User objects cannot be created in the specified container
- Next by thread: Re: User objects cannot be created in the specified container
- Index(es):
Relevant Pages
|