[horde] Turba LDAP Contact Lists

[Simon Wilson]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Simon Wilson <simon at simonandkate.net>:
>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>>> Zitat von Simon Wilson <simon at simonandkate.net>:
>>>
>>>> I have Turba 2.3.1 in an LDAP backend configuration (Horde
>> 3.3.4rc1).
>>>>
>>>> LDAP address books are working fine, shared and personal, for
add
>> /
>>>> edit / delete. However when I try and create a Contact List
>> (select
>>>> contacts, Add to a Contact List - Shared Address Book, give it a

>>>> name), it tells me "There was an error creating a new list".
>>>>
>>>> My LDAP server has the following error message:
>>>>
>>>> Apr 14 10:57:34 server01 slapd[2776]: conn=2475 op=2 RESULT
>> tag=105
>>>> err=65 text=object class 'inetOrgPerson' requires attribute 'sn'
>>>>
>>>> It is generating a name for it OK - previous LDAP log entry is:
>>>>
>>>> server01 slapd[2776]: Entry
>>
(uid=20090414105734.18132bcih8razipq at mail.simonandkate.net,ou=simon,ou=personal_addressbook,dc=simonandkate,dc=lan):
>> object class 'inetOrgPerson' requires attribute
>>>> 'sn'
>>>>
>>>> Is there a way to tell the submission query to not try and use  
>>>> inetOrgPerson for a new list entry as opposed to a new contact?
>>>
>>> No. Both, individual contacts and address lists, require the same

>>> object classes at the moment.
>>>
>>>> Also, can someone please confirm - I have Horde LDAP Groups  
>>>> (Administration - Groups) working fine, creating new groups,
>> adding
>>>> members, etc, but that is just for permissions isn't it, not  
>>>> membership lists or anything like that? I haven't been able to
>> find
>>>> much about Horde Groups online...
>>>
>>> What do you mean with member ship lists? There are a few other
>> places
>>> where groups can be used, there is an address book driver for  
>>> example, that can display other members of the user's groups. But
>> the
>>> main purpose is permissions/sharing, yes.
>>>
>>> Jan.
>>>
>>> -- 
>>> Do you need professional PHP or Horde consulting?
>>> http://horde.org/consulting/
>>>
>>> --
>>> Horde mailing list - Join the hunt:
>> http://horde.org/bounties/#horde
>>> Frequently Asked Questions: http://horde.org/faq/
>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>>
>>>
>>>
>>
>> Thanks Jan for the response.
>>
>> So basically, as Turba does not ask for enough information to  
>> populate the required attributes of the LDAP object classes when  
>> creating a contact list, Turba Contact Lists with an LDAP backend  
>> are currently not operational?
>
> Of course it is, as long as both require the same set of object
classes.
>
> Jan.
>
> -- 
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
>
> --
> Horde mailing list - Join the hunt:
http://horde.org/bounties/#horde
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>
>
>

"...as long as both require the same set of object
classes."

Adding a Contact List asks you for only one parameter - the Contact  
List name. With Contact List creation using the same Object Classes as  
when you add a Contact, for it to successfully create a Contact List  
with only the single attribute asked for you cannot use the "person",  
"inetorgperson", or "organisationalperson" object classes for Contacts  
- all of which require "cn" and "sn" attributes.

With those classes enabled so Contacts have a meaningful set of  
attributes adding a Contact List throws an object class violation.

To me having to disable those basic object classes to make Contact  
Lists work makes Contact Lists not operational with an LDAP backend...  
unless I am missing something obvious...


-- 
Simon Wilson
www.simonandkate.net