RE: restricting attributes to become RDN , which objects are created

Hello Gavin,

Thanks for the reply. If this restriction is not there, any of the users can create a dn with RDN as any attribute, which leads to non-uniformity (for instance, one user may create uid as RDN and other may use userPassword as RDN for inetOrgPerson)

Thanks in advance,

Arunachalam.

**************************************************************************** ****************************

This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-----Original Message----- From: Gavin Henry [mailto:ghenry@suretecsystems.com] Sent: Monday, October 01, 2007 4:02 AM To: arunachalamp@huawei.com Cc: openldap-software@openldap.org Subject: Re: restricting attributes to become RDN , which objects are created

Arunachalam Parthasarathy wrote:

Hello all,

In objectclass, Is there a way to restrict (only) an attribute to be RDN?

For ex: only uid needs to be RDN , in organizational Unit

Thanks in advance,

Why?