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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11888
------------------------------------------------------------------------------
  Ticket             | 11888
  Updated By         | horde at iotti.biz
  Summary            | Add possibility for composite RDNs in LDAP
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Enhancement
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


horde at iotti.biz (2014-06-04 07:31) wrote:

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