Hei LDAP gurus listening on RCD
I try to write a howto for a simple LDAP server setup, such that LDAP dummies out there should be able to setup a server from scratch working with RC "out of the box". (No, I do not write it for you if you are knowing how to setup a LDAP server yourself! Just for beginners how I have been some month ago:-)
My first question is, what structure should such a server have... I know, there exist a plenty of professional solutions, but what I want is just:
- a verry good RC support, including especially groups
- good support for other clients (Thunderburd, Kaddressbook, Outlook, ...) ( if they do not support groups as we do, it sould at least be possible to
read/write contacts)
- RC must stay compatible with other LDAP servers as it is today
Now, what structure do I propose? I prefere two different directory trees:
- Addressbook directory with grouping subdirectories:
# the base dn: ou=rcaddrbook,dc=localhost # some groups: dn: ou=Group1,ou=rcaddrbook,dc=localhost dn: ou=Group2,ou=rcaddrbook,dc=localhost # some contacts dn: cn=Conact 1,ou=Group1,ou=rcaddrbook,dc=localhost dn: cn=Conact 2,ou=Group1,ou=rcaddrbook,dc=localhost dn: cn=Conact 3,ou=Group2,ou=rcaddrbook,dc=localhost
-> this structure works fine with one restriction: having a contact in two groups means having duplicates, and this is bad but this is easy to use in RC and even in Kaddressbook while crating a static addressbook per group (RC will learn to read the group-list soon if needed)
- Addressbook directory with seperate group list in a sub, contacts and
groups are connected with the member attribute: # the base dn: ou=rcaddrbook,dc=localhost # group and member dirs dn: ou=Groups,ou=rcaddrbook,dc=localhost dn: ou=Members,ou=rcaddrbook,dc=localhost # some groups (not all attributes shown here!) dn: cn=Group1,ou=Groups,ou=rcaddrbook,dc=localhost member: cn=Contact 1,ou=Members,ou=rcaddrbook,dc=localhost member: cn=Contact 2,ou=Members,ou=rcaddrbook,dc=localhost dn: cn=Group2,ou=Groups,ou=rcaddrbook,dc=localhost member: cn=Contact 3,ou=Members,ou=rcaddrbook,dc=localhost # some members dn: cn=Contact 1,ou=Members,ou=rcaddrbook,dc=localhost dn: cn=Contact 2,ou=Members,ou=rcaddrbook,dc=localhost dn: cn=Contact 3,ou=Members,ou=rcaddrbook,dc=localhost
-> this structure works fine on my server, including memberOf search just in the "Members" subdir. I do not know the restrictions of this structure yet, clients like RC and Kaddressbook again can access at least with "addressbook per group", but again, RC will learn to get the grouplist soon (if wanted)
What do you think about that? Is there any chance to access even the group feature with other modern clients? how?
thank you for your feedback
Andreas _______________________________________________ List info: http://lists.roundcube.net/dev/ BT/aba52c80