--0016e6520602e44cff0462e14152 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On Sat, Feb 14, 2009 at 11:17 PM, Pierangelo Masarati ando@sys-net.itwrote:
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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote">On Sat, Feb 14, 2009 at 11:17 PM, Pierangelo Mas= arati <span dir=3D"ltr"><<a href=3D"mailto:ando@sys-net.it">ando@sys-net= .it</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"bor= der-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-= left: 1ex;">
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 sen= se, but not in your case). This issue should now be fixed in HEAD.<br=
<br> Note that entryDN and subschemaSubentry are not leaked by slapd-meta(5): th= ey're actually generated by the frontend. This should be prevente= d now. Please re-test.</blockquote><div><br>Yep all looks good now, u= sing either the meta backend, or the ldap + rwm overlay.<br> <br>Good work :)<br></div></div><br>
--0016e6520602e44cff0462e14152--