| Summary | Multivalued RDN not working with LDAP |
| Queue | Turba |
| Queue Version | Git master |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | willem.verbruggen (at) anagky (dot) be |
| Created | 01/26/2009 (6017 days ago) |
| Due | |
| Updated | 02/02/2016 (3454 days ago) |
| Assigned | 01/27/2009 (6016 days ago) |
| Resolved | 02/02/2016 (3454 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Taken from Ben Klang
Taken from Gunnar Wrobel
State ⇒ Duplicate
Version ⇒ Git master
request #11889me to have to fix this manually every time I update turba. Someone has
written a patch for this that works for me, see:
http://lists.horde.org/archives/turba/Week-of-Mon-20090525/006162.html
but I'm concerned what the change will do to existing installations.
It may be that the existing code works for some people, even if it is
not the correct way. However I *think* that the current behavior can
not work under "normal" circumstances because it assumes that parent
objects will be created implicitly when that is actually impossible.
To be perfectly honest, until this bug was reported I wasn't even
aware that LDAP supported multi-attribute DNs, but it does make sense
now that I have read about it.
I am going to move forward with applying the fix as suggested because
I think the current behavior is actually broken. In any case I was
not able to get it to work reliably on my test systems and this will
make it work.
Assigned to Gunnar Wrobel
Assigned to Ben Klang
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Multivalued RDN not working with LDAP
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
New Attachment: Turbabug
State ⇒ Unconfirmed
that are unique, I configured the setting 'dn' => array('cn','sn').
Turba loads existing addressbook entries just fine but when I tried to
update existing entries or adding new ones, this failed because it
seems the RDN was built with cn=data,sn=data instead of
cn=data+sn=data. See attached LDAP error log for details.