[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Customizing organizationalUnit
- To: Michael StrÃder <michael@stroeder.com>
- Subject: Re: Customizing organizationalUnit
- From: Erwann ABALEA <eabalea@gmail.com>
- Date: Sat, 6 Aug 2011 16:03:02 +0200
- Cc: harry.jede@arcor.de, openldap-technical@openldap.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=K+Ri57z54bF6wNj9fkjgi3WJH2F4+tnCp+FJlGmcfIA=; b=lW9v5li279jg2A72mwV7toRYqF3qf9Gm5nMPH8YNz933XFqTOQPVyOn6joNNALT1Tx vilobd00mbMmZJjNH4PCp37iYFqfmpoh4zykeHlY6bEa5GVoV2EEF+C1NxwhS4iM3eKf ObQnVEtJFs73Yu9rTPk/U4ycey0UL2Jqzji5k=
Le 6 aoÃt 2011 15:49, "Michael StrÃder" <michael@stroeder.com> a ÃcritÂ:
>
> harry.jede@arcor.de wrote:
> > The cleanest approach is to modify your OU entries:
> >
> > objectClass: top
> > objectClass: organizationalUnit
> > objectClass: extensibleObject
> >
> > Now, all attributes which are defined in any schema are allowed :-) .
>
> That's what I consider bad advice and definitely not the cleanest approach.
This is equivalent to your solutions 1 and 2, described 3 days ago.