Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates
 74.125.82.178 as permitted sender)
Sender: Pierre-Arnaud Marcelot <pajbam@gmail.com>
From: Pierre-Arnaud Marcelot <pa@marcelot.net>
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_74D75748-FFC8-4B28-B2BF-319FB3FBC657"
Subject: Re: Renaming an entry with a case insensitive RDN : how to handle it
 ?
Date: Wed, 15 Feb 2012 14:39:50 +0100
In-Reply-To: <4F3BB270.1050907@gmail.com>
To: "Apache Directory Developers List" <dev@directory.apache.org>,
 elecharny@apache.org
References: <4F3BB270.1050907@gmail.com>
Message-Id: <4544E65F-6361-426C-9256-6276B6CAB9FE@marcelot.net>


--Apple-Mail=_74D75748-FFC8-4B28-B2BF-319FB3FBC657
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On 15 f=E9vr. 2012, at 14:26, Emmanuel L=E9charny wrote:

> Hi guys,
>=20
> let's suppose we have an entry like :
>=20
> dn: cn=3Djohn doe, ou=3Dsystem
> objectclass: person
> cn: john doe
> sn: john doe
>=20
> Let's now suppose that we want to camel-case the cn to have an entry =
like :
>=20
> dn: cn=3DJohn Doe, ou=3Dsystem
> objectclass: person
> cn: John Doe
> sn: john doe
>=20
> Currently ADS does not support such a modification : it considers that =
it's a modifcation of an entry on itself, and it's not allowed. (cn is =
case insensitive, so basically, it's really a modification on itself).

Here's the exact error message it returns:
> LDAP: error code 68 - Attempt to move entry onto itself.


The error message is the same whether we use the LDAP API or JNDI in =
Studio.

I tested the same thing on OpenLDAP and the modification is successful.

> Now, from the user PoV, this is a bit painful, because even if cn is =
case insensitive, the user wants to see the DN as he provided it (after =
the rename, he may expect dn: cn=3DJohn Doe, ou=3Dsystem).
>=20
> So
>=20
> Q1 : should we allow such a rename ? (it will modify the RDN *and* the =
attribute)

=46rom the server's POV, the value, once normalized, is exactly the same =
('cn' is case insensitive). So I understand the rejection.
Now, from a user's POV, it would be better if it worked.

So, I'd go +1.

> Q2 : if we modify the cn only, should the RDN be modified too ? =
(currently, ADS does modify the CN, but not the RDN)

+1 too.

Regards,
Pierre-Arnaud

> wdyt ?
>=20
> --=20
> Regards,
> Cordialement,
> Emmanuel L=E9charny
> www.iktek.com
>=20


--Apple-Mail=_74D75748-FFC8-4B28-B2BF-319FB3FBC657
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On 15 f=E9vr. 2012, at 14:26, Emmanuel L=E9charny =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi guys,<br><br>let's suppose we have an entry like =
:<br><br>dn: cn=3Djohn doe, ou=3Dsystem<br>objectclass: person<br>cn: =
john doe<br>sn: john doe<br><br>Let's now suppose that we want to =
camel-case the cn to have an entry like :<br><br>dn: cn=3DJohn Doe, =
ou=3Dsystem<br>objectclass: person<br>cn: John Doe<br>sn: john =
doe<br><br>Currently ADS does not support such a modification : it =
considers that it's a modifcation of an entry on itself, and it's not =
allowed. (cn is case insensitive, so basically, it's really a =
modification on =
itself).<br></div></blockquote><div><br></div><div>Here's the exact =
error message it returns:</div><div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-indent: =
1.1px; font: normal normal normal 11px/normal 'Lucida Grande'; =
"><blockquote type=3D"cite">LDAP: error code 68 - Attempt to move entry =
onto itself.</blockquote></div></div><div><br></div><div>The error =
message is the same whether we use the LDAP API or JNDI in =
Studio.</div><div><br></div><div>I tested the same thing on OpenLDAP and =
the modification is successful.</div><br><blockquote =
type=3D"cite"><div>Now, from the user PoV, this is a bit painful, =
because even if cn is case insensitive, the user wants to see the DN as =
he provided it (after the rename, he may expect dn: cn=3DJohn Doe, =
ou=3Dsystem).<br><br>So<br><br>Q1 : should we allow such a rename ? (it =
will modify the RDN *and* the =
attribute)<br></div></blockquote><div><br></div><div>=46rom the server's =
POV, the value, once normalized, is exactly the same ('cn' is case =
insensitive). So I understand the rejection.</div><div>Now, from a =
user's POV, it would be better if it =
worked.</div><div><br></div><div>So, I'd go +1.</div><br><blockquote =
type=3D"cite"><div>Q2 : if we modify the cn only, should the RDN be =
modified too ? (currently, ADS does modify the CN, but not the =
RDN)<br></div></blockquote><div><br></div><div>+1 =
too.</div><div><br></div><div>Regards,</div><div>Pierre-Arnaud</div><br><b=
lockquote type=3D"cite"><div>wdyt ?<br><br>-- =
<br>Regards,<br>Cordialement,<br>Emmanuel L=E9charny<br><a =
href=3D"http://www.iktek.com">www.iktek.com</a><br><br></div></blockquote>=
</div><br></body></html>=

--Apple-Mail=_74D75748-FFC8-4B28-B2BF-319FB3FBC657--