Tickets :: Comment on [#11888] Add possibility for composite RDNs in LDAP

* Your Email Address
* Spam protection	Enter the letters below: __.. ..___.__ . , (__ \|_/ [__ [__) \./ .__)\| \\| \| \ \|
Comment	> I would like to submit a minimally modified patch which, building the > composite RDN, does not include void attibutes. > For example, say that you have some ldap account made this way: > cn: John > sn: Smith > o: Acme inc > --- > cn: Mike > sn: Smith > o: Acme inc > --- > cn: John > sn: Smith > o: > > In this case, if I use cn+sn+o to build the RDN, I would end up with > a RDN like cn=John+sn=Smith+o= for the latter contact, which is > invalid. cn=John+sn=Smith (without o=) would be valid instead. The > included modified patch does this. > The example should also fit for the old example request by Jan. I use > composite RDNs to be able to store my accounts in LDAP: the accounts > would collide if I used only a single attribute for the RDN, be it > the first name, surname, organization... > > I'm using this patch (or older versions which appeared in the ML and > the web) since Turba 2, so I would like to ask for inclusion in the > main distribution, together with http://bugs.horde.org/ticket/11889 > which is closely related to this. > > Thanks
Attachment
Watch this ticket