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

Re: cn=config default access control

To: Derek Zhou <derek@shannon-data.com>, openldap-technical@openldap.org
Subject: Re: cn=config default access control
From: Quanah Gibson-Mount <quanah@symas.com>
Date: Fri, 16 Nov 2018 15:37:40 -0800
Content-disposition: inline
In-reply-to: <20181116021129.6ir5u5iw3xhvcoik@shannon-data.com>
References: <20181116021129.6ir5u5iw3xhvcoik@shannon-data.com>

--On Friday, November 16, 2018 10:11 AM +0800 Derek Zhou<derek@shannon-data.com> wrote:

My argument is why isn't it the default?


A couple of immediate answers come to mind, there are probably more:

a) OpenLDAP is used on numerous operating systems. Not all of thoseoperating systems support UNIX sockets.


b) Not everyone configures slapd for use with ldapi

By the way, if we really want people to use cn=config exclusively, I
suggest to remove all mentioning of slapd.conf from the latest
documentation. Old admins  appreciate cn=config more and there will be
less distraction for newbies.

Once cn=config is the only way to configure OpenLDAP, such documentationwill be removed. However, that won't be occurring in OpenLDAP 2.5, whichis the next major release, so it is valid for this documentation to remainin OpenLDAP master for the time being.


--Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>

Follow-Ups:
- Re: cn=config default access control
  - From: Derek Zhou <derek@shannon-data.com>

References:
- cn=config default access control
  - From: Derek Zhou <derek@shannon-data.com>

Prev by Date: cn=config default access control
Next by Date: Re: cn=config default access control
Index(es):
- Chronological
- Thread