From brett.maxfield@gmail.com Fri Oct 31 07:10:09 2008
From: brett.maxfield@gmail.com
To: openldap-bugs@openldap.org
Subject: Re: (ITS#5760) attribute hiding in rwm overlay
Date: Fri, 31 Oct 2008 07:10:09 +0000
Message-ID: <200810310710.m9V7A9Kq018526@boole.openldap.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4521298516768097036=="

--===============4521298516768097036==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

------=3D_Part_28816_12585104.1225436998930
Content-Type: text/plain; charset=3DISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

trying some different things with the last release.

very interesting that rwm-map works with operational attributes, i can see
hasSubordinates, subschemaSubentry, entryUUID but not the other
non-operational attributes such as cn, sn,
etc., do not show..

# these dont
rwm-map attribute cn *
rwm-map attribute sn *
rwm-map attribute givenName *
rwm-map attribute mail *
rwm-map attribute c *
rwm-map attribute o *
rwm-map attribute ou *

# these work
rwm-map attribute hasSubordinates *
rwm-map attribute subschemaSubentry *
rwm-map attribute entryUUID *

# this enabled
rwm-map attribute *

On Tue, Oct 21, 2008 at 3:55 PM, Pierangelo Masarati <ando(a)sys-net.it>wrote:

> Not clear what the problem is, now.  The above configuration seems to work
> as intended as far as attribute mapping is concerned.  The fact that
> "rwm-map objectclass *" no longer kills the objectClass attribuet was fixed
> some time ago (the fix is in 2.4.12).  What kills the allowed objectClass
> values is a bug in evaluating what values are preserved.  If you don't put
> any "rwm-map objectclass" rule, it works as expected.
>
> I'm fixing this other bug.
>
>

------=3D_Part_28816_12585104.1225436998930
Content-Type: text/html; charset=3DISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

trying some different things with the last release.<br><br>very
interesting that rwm-map works with operational attributes, i can see
hasSubordinates, subschemaSubentry, entryUUID but not the other
non-operational attributes such as cn, sn,<br>etc., do not show..<br>
<br># these dont<div class=3D"Ih2E3d"><br>rwm-map attribute cn *<br>rwm-map a=
ttribute sn *<br></div>rwm-map attribute givenName *<div class=3D"Ih2E3d"><br=
>rwm-map attribute mail *<br>rwm-map attribute c *<br>rwm-map attribute o *<b=
r>
rwm-map attribute ou *<br><br></div># these work<br>
rwm-map attribute hasSubordinates *<br>rwm-map attribute subschemaSubentry *<=
br>rwm-map attribute entryUUID *<br><br># this enabled<br>rwm-map attribute *=
<br><br><div class=3D"gmail_quote">On Tue, Oct 21, 2008 at 3:55 PM, Pierangel=
o Masarati <span dir=3D"ltr">&lt;<a href=3D"mailto:ando(a)sys-net.it">ando(a)=
sys-net.it</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 20=
4, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Not clear what the pr=
oblem is, now. &nbsp;The above configuration seems to work as intended as far=
 as attribute mapping is concerned. &nbsp;The fact that &quot;rwm-map objectc=
lass *&quot; no longer kills the objectClass attribuet was fixed some time ag=
o (the fix is in 2.4.12). &nbsp;What kills the allowed objectClass values is =
a bug in evaluating what values are preserved. &nbsp;If you don&#39;t put any=
 &quot;rwm-map objectclass&quot; rule, it works as expected.<br>

<br>
I&#39;m fixing this other bug.<br>
<br></blockquote></div><br>

------=3D_Part_28816_12585104.1225436998930--



--===============4521298516768097036==--