[Tickets #6263] Re: Problem adding contact groups when using composite fields (LDAP)

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=6263
-----------------------------------------------------------------------
 Ticket             | 6263
 Updated By         | dirk at liji.de
 Summary            | Problem adding contact groups when using composite fields (LDAP)
 Queue              | Turba
 Version            | 2.2-RC2
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Milestone          | 
 Patch              | 
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


dirk at liji.de (2008-02-15 18:56) wrote:

...
        'dn' => array('uid'),
        'objectclass' => array('locality',
                               'uidObject',
                               'turbaContact'),
    ),
    'map' => array(
        '__key' => 'dn',
        '__uid' => 'uid',

        // From horde.schema:
        '__type' => 'turbaType',
        '__members' => 'turbaMembers',

        'name' => 'l',
    ),
    'search' => array(
        'name',
    ),
    'strict' => array(
        'dn',
    ),
    'approximate' => array(
        'l',
    ),
    'export' => true,
    'browse' => true,
    'list_name_field' => 'name',
);

This is part of the test configuration, no composite field name, since
it's locality as structural objectclass it doesn't requite any attribute
anymore, with uidObject just a uid. The name is mapped to the 'l' attribute
of the locality.
Now, whenever i add a group the group doesn't get a name at all, it's
listed with an empty name.
The corresponding ldap entry is (with replaced private information)

dn: uid=20080216003157.*************@*************.de,ou=Groups,
 o=turba,dc=*****,dc=*******,dc=de
uid: 20080216003157.****************@**************.de
turbaType: Group
turbaMembers:
a:1:{i:0;s:119:"lsldap:uid=20080130145215.**************@***
 ***************.de,ou=Addressbook,o=turba,dc=*****,dc=**********,dc=de";
 }
objectClass: locality
objectClass: uidObject
objectClass: turbaContact

The entry doesn't contain the 'l' attribute at all, so it doesn't contain
the name, it is as if the name was not sent to the server.
(Ok, honestly, since the 'list_name_field' is not documented i guessed
it's use so it's possible there's a problem in the configuration.)
I hope this example gives a better view to the problem i'm facing.

Dirk.