[Tickets #9554] store multiple email addresses as separate 'mail' attributes in LDAP
bugs at horde.org
bugs at horde.org
Sun Jan 30 15:29:54 UTC 2011
BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE
E-MAIL-ADRESSE WERDEN NICHT GELESEN.
Ticket-URL: http://bugs.horde.org/ticket/9554
------------------------------------------------------------------------------
Ticket | 9554
Erstellt Von | tgpfeiffer at web.de
Zusammenfassung | store multiple email addresses as separate 'mail'
| attributes in LDAP
Warteschlange | Turba
Version | 2.3.4
Typ | Bug
Status | Unconfirmed
Priorität | 1. Low
Milestone |
Patch |
Zuständige |
------------------------------------------------------------------------------
tgpfeiffer at web.de (2011-01-30 10:29) hat geschrieben:
My Turba uses an LDAP backend, and I wondered how people could have
more than one email address. Obviously, LDAP supports multiple 'mail'
attributes per inetOrgPerson and when setting
'allow_multi' => true
in turba/config/attributes.php, they are also treated as separate
email addresses and each 'mail' entry results in a separate
mailto-link in Turba.
However, when editing the email field, there is a comma-separated list
of addresses which is written back into LDAP *as is*. This causes
problems, because, for example, it's not possible any more to do an
LDAP query with "(mail=address1 at host.com)". Instead, the LDAP backend
- just as it converts multiple 'mail' attribute values to a PHP array
- should act the same when saving, i.e. converting the PHP array (or
the comma-separated string) into multiple LDAP attributes.
More information about the bugs
mailing list