From brett.maxfield@gmail.com Sat Feb 14 13:52:09 2009 From: brett.maxfield@gmail.com To: openldap-bugs@openldap.org Subject: Re: (ITS#5760) attribute hiding in rwm overlay Date: Sat, 14 Feb 2009 13:52:08 +0000 Message-ID: <200902141352.n1EDq80x007204@boole.openldap.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6886783616402816836==" --===============6886783616402816836== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable --0016e6520602e44cff0462e14152 Content-Type: text/plain; charset=3DISO-8859-1 Content-Transfer-Encoding: 7bit On Sat, Feb 14, 2009 at 11:17 PM, Pierangelo Masarati wrot= e: > The missing operational attrs are my fault: I erroneously tested back-meta > with slapo-rwm's mapping, instead of the native one (which may make sense, > but not in your case). This issue should now be fixed in HEAD. > > Note that entryDN and subschemaSubentry are not leaked by slapd-meta(5): > they're actually generated by the frontend. This should be prevented now. > Please re-test. Yep all looks good now, using either the meta backend, or the ldap + rwm overlay. Good work :) --0016e6520602e44cff0462e14152 Content-Type: text/html; charset=3DISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sat, Feb 14, 2009 at 11:17 PM, Pierangelo Mas= =3D arati <ando(a)s= ys-net=3D .it> wrote:
The missing operational attrs are my fault: I erroneously tested back-meta =3D with slapo-rwm's mapping, instead of the native one (which may make sen=3D se, but not in your case).  This issue should now be fixed in HEAD.
Note that entryDN and subschemaSubentry are not leaked by slapd-meta(5): th=3D ey're actually generated by the frontend.  This should be prevente=3D d now.  Please re-test.

Yep all looks good now, u=3D sing either the meta backend, or the ldap + rwm overlay.

Good work :)

--0016e6520602e44cff0462e14152-- --===============6886783616402816836==--