On Fri, 2011-10-21 at 10:37 +0200, Andrey Ivanov wrote:
> Hi,
>
> we are using 389 in production environment since 2006 or 2007. It is a
> central authentication/authorization mechanism for ~2 accounts,
> ~500 (occasional search from 5000) workstations, ~20-30 web
> applications.
> We have 3
Hello, all. I know one can only have one sync agreement with an AD.
However, is it possible to have a sync agreement with multiple ADs. We
would like to synchronize the top of our tree with our main,
multi-tenant AD and then synchronize lower levels of the domains with
separate domains controlled
On Tue, 2010-07-20 at 23:15 -0400, John A. Sullivan III wrote:
> On Tue, 2010-07-20 at 18:08 -0400, John A. Sullivan III wrote:
> > On Tue, 2010-07-20 at 14:15 -0400, John A. Sullivan III wrote:
> > > On Tue, 2010-07-20 at 10:05 -0600, Rich Megginson wrote:
> >
On Tue, 2010-07-20 at 10:05 -0600, Rich Megginson wrote:
> --[ UxBoD ]-- wrote:
> > - Original Message -
> > >
> >
> >>
> >> ? Note that winsync will not add sub-ou containers
> >
> > In AD we have the standard mappings of CN=Users,DC=ad,DC=domain,DC=com and
> > we are trying to sync a
On Thu, 2010-05-06 at 14:45 -0400, Prashanth Sundaram wrote:
> I got around this by changing the ldap.conf.
>
> pam_filter objectclass=posixAccount
> pam_member_attribute uniquemember
>
> I haven;t tested this but you can also map the memberuid and memberof
> to Uniquememember. So the nss_ldap ch
On Mon, 2010-03-29 at 13:30 -0600, Rich Megginson wrote:
> John A. Sullivan III wrote:
> > Hello, all. We are experiencing a weird problem and have not been able
> > to fix it. We have just renamed the top level of our tree from
> > dc=old,dc=biz to dc=new,dc=com. All went
Hello, all. We are experiencing a weird problem and have not been able
to fix it. We have just renamed the top level of our tree from
dc=old,dc=biz to dc=new,dc=com. All went very well (well, very well
until we also changed the certificates and keys to be from the new
Certificate Authority - but
Hello, all. We've recently undergone a corporate name and domain
change, let's say from oldname.biz to newname.com. Consequently, we
need to rename the top level of our LDAP structure. We installed CentOS
Directory Server 8.1 into dc=oldname,dc=biz and now need that entire
structure to have dc=n
