[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Index Alias Attribute
- To: Josh Catana <jcatana@gmail.com>, openldap-technical@openldap.org
- Subject: Re: Index Alias Attribute
- From: Quanah Gibson-Mount <quanah@symas.com>
- Date: Thu, 13 Jul 2017 16:56:53 -0700
- Content-disposition: inline
- In-reply-to: <WM!649e4f02533722a12e00ed95c4b62cecb2136423a3422af33c42e455fc5fa1aec9d31b3634f961de78edd1612b2255b1!@mailstronghold-2.zmailcloud.com>
- References: <CAJOKg0TkTSHdWZ0Pgt6zrNoF1O+mbUWyJK=F4WsHzY8HbUFzgQ@mail.gmail.com> <WM!649e4f02533722a12e00ed95c4b62cecb2136423a3422af33c42e455fc5fa1aec9d31b36 34f961de78edd1612b2255b1!@mailstronghold-2.zmailcloud.com>
--On Thursday, July 13, 2017 11:35 AM -0400 Josh Catana <jcatana@gmail.com>
wrote:
Running on sles11sp3 openldap2-2.4.26-0.62.2
BDB backend.
Hm:
OpenLDAP 2.4.26 Release (2011/06/30)
OpenLDAP 2.4.45 Release (2017/06/01)
Getting a bit crufty there. ;)
We heavily rely on aliases to different OUs to manage access to different
environments, prod/dev/qa/etc.
Expand on what you mean by aliases, please. In general, using aliases in
LDAP is a bad idea.
I know I should probably update the backend, but this isn't what the
question is about.
back-mdb is awful with aliases (See
<http://www.openldap.org/its/index.cgi/?findid=7657>), so I'm not sure
changing backends would help.
You may be hitting <http://www.openldap.org/its/index.cgi/?findid=7743>,
there was no further follow up on it.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>