[Date Prev][Date Next] [Chronological] [Thread] [Top]

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


Hello quanah,

Sorry that i had not sent mail to the group...

Below is the answer for your question

"Actually I was saying the above for an example, I asked in a view that, if this restriction is there from server side. Then strict enforcement can be done (if needed)"

Thanks a lot,



 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: Quanah Gibson-Mount [mailto:quanah@zimbra.com]
Sent: Monday, October 01, 2007 9:05 PM
To: arunachalamp@huawei.com; openldap-software@openldap.org
Subject: RE: restricting attributes to become RDN , which objects are created


--On Monday, October 01, 2007 3:23 PM +0530 Arunachalam Parthasarathy

<arunachalamp@huawei.com> wrote:




> 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)


Why do you let users create their own objects?






Quanah Gibson-Mount

Principal Software Engineer

Zimbra, Inc


Zimbra ::  the leader in open source messaging and collaboration