Grouper Users - Open Discussion List

[Tom Zeller <>]

At Memphis, we make sure that our Active Directory RDNs are unique,
whether they be users, groups, contacts, etc., and these RDNs are
provisioned to sAMAccountName. Whenever a new person, group, or
contact is created, we check our namespace for uniqueness.

Silly, but, you might get away with adding a prefix to sAMAccountName
for groups.

On Wed, Mar 9, 2011 at 5:59 PM, Mailvaganam, Hari
<>
 wrote:
> Hi:
>
>
>
> We are looking at pushing groups from Grouper, via LDAPPCNG, to Active
> Directory (AD).
>
>
>
> In example scenario below, for group and person, there will be a clash in
> sAMAccountName – would you have any suggestions on policies, or rules, to
> avoid similar conflict?
>
>
>
> GROUP
>
>
>
> Distinguished Name (DN):
> CN=science,OU=Groups,OU=IT,OU=example,OU=Clients,DC=example,DC=edu
>
>
>
> sAMAccountName: science
>
>
>
>
>
> PERSON
>
>
>
> Distinguished Name (DN):
> CN=science,OU=People,OU=IT,OU=example,OU=Clients,DC=example,DC=edu
>
>
>
> sAMAccountName: science
>
>
>
> Thanks.
>
>
>
> Best regards,
>
>
>
> Hari
>
>