[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4035) rootdn incorrect in cn=config backend/database

tonye@billy.demon.nl wrote:
> This is a multi-part message in MIME format.
> --------------090007030100010708080707
> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
> Content-Transfer-Encoding: 7bit
> 2.3.9: Agreed with Andreas, only I can actually change any cn=config
> hierarchy attribute, even though i get the "insufficient access" denial.
> Compile and access details attached.
A couple of comments:
    you can just use configure --enable-overlays if you want them all...
    the cn=config database ignores ACLs. It requires you to be the 
rootdn to have any access at all.

And yes, we need to write a manpage for the config backend. That's 
already ITS#3812. Anyone who wants to volunteer to help get that going 
can probably start by condensing some of the information that's 
currently in the Admin Guide into manpage format.

  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/