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

Re: Null suffix as default (ITS#723)

I think adding a "defaultNamingContext" (defaultSuffix) option is
much more reasonable then supporting suffix "" for any other
use than hosting the root naming context.

Of course, the implementation needs to be careful not to interfere
with root DSE searches.

Thanks for the suggestion and the patch.


At 08:06 PM 9/10/00 +0000, pmasarati@bci.it wrote:
>Full_Name: Pierangelo Masarati
>Version: 2.0.1
>OS: Linux
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (
>In OpenLDAP 1.2 and earlier I could set an ldbm backend suffix as:
>suffix "o=My Org,c=IT"
>suffix ""
>and this used to allow to operate searches on the backend with a null search
>base, e.g.
>ldapsearch -b "" objectclass=*
>would yield all the entries with base "o=My Org,c=IT"
>This is no longer true in OpenLDAP 2.0; I temporarily fixed the problem with
>the patch you may find at 
>by adding a configuration directive 
>defaultSuffix   "o=My Org,c=IT"
>which allows to substitute a null ("") search base with the default one (it is
>by adding --enable-default-suffix-hack at configure time). This feature is key
>to my 
>application, because I should otherwise reconfigure some 25,000 clients which
>work with a "" base on a directory with non-null suffix.
>The point is: was the feature I mentioned intended in OpenLDAP 1.2 or was it
>kind of
>a bug? And in case it was intended, why isn't it supported any longer in
>OpenLDAP 2.0?
>If my patch seems reasonable, feel free to use it; there is no copyright notice
>since it is nothing but a few lines of code. If you need one, let me know.
>Bye, Pierangelo Masarati