[Bug 571057] Re: slapd 2.4.21-0ubuntu5 corrupts olcDatabase={-1}frontend.ldif with duplicate olcAccess lines (again)

[Nathan Stratton Treadway]

As touched on in the discussion for bug #563829, the release notes
should also mention that after upgrading to slapd 2.4.21-0ubuntu5, the
user will need to manually clean up the slapd config files in order to
complete the switch from the use of the "cn=localroot,cn=config" mapping
to the direct use of the
"gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth" identifier in
the security configuration.  (This is true even when slapd does start up
successfully after the upgrade.)

As far as I can tell from my own testing, this cleanup would involve
removing any olcAccess lines referencing "cn=localroot,cn=config" from
all /etc/ldap/slapd.d/cn=config/olcDatabase*.ldif files, and also
removing the olcAuthzRegexp line mentioning that identifier from the
/etc/ldap/slapd.d/cn=config.ldif file.

-- 
slapd 2.4.21-0ubuntu5 corrupts olcDatabase={-1}frontend.ldif with duplicate olcAccess lines (again)
https://bugs.launchpad.net/bugs/571057
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.