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

(ITS#7525) Bad conversion to cn=config format

Full_Name: Francesco Policastro
Version: 2.4.33
OS: RHEL 6.2
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (

A slapd.conf using meta backend can include the following uri definition that is
accepted as legal

uri "ldap://server2.domain2.net/ou=org Unit,dc=second,dc=newco,dc=com"
idassert-bind bindmethod=simple binddn="cn=ldap-2,cn=Users,dc=domain2,dc=net"
chase-referrals no
rebind-as-user true
map objectclass groupOfNames *
map objectclass person *
suffixmassage "dc=second,dc=newco,dc=com" "dc=domain2,dc=net"
subtree-include "ou=Users,ou=1stlocation,ou=org Unit,dc=second,dc=newco,dc=com"

"slaptest -f slapd.conf" returns "config file testing succeeded"
"slaptest -f slapd.conf -F slapd.d" converts to cn=config format
"slaptest -F slapd.d" issues an error:
511a57ef olcDbURI: value #0: unable to parse URI #0 in "olcDbURI
<protocol>://<server>[:port]/<naming context>".
511a57ef config error processing
olcMetaSub={1}uri,olcDatabase={1}meta,cn=config: unable to parse URI #0 in
"olcDbURI <protocol>://<server>[:port]/<naming context>"
slaptest: bad configuration directory!

I know that the offending words are in the "ou=org Unit" directive; in fact
"ou=orgUnit" (with no space) works.

The uri sintax permits to enclose the string in quotes and one assumes that
spaces are legal. They are only in slapd.conf because the cn=config conversion
does not accept them.