Changes between Version 3 and Version 4 of Howto_Config_LDAP


Ignore:
Timestamp:
Dec 1, 2011 3:08:40 PM (2 years ago)
Author:
andudi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Howto_Config_LDAP

    v3 v4  
    33This howto describes the mapping of the contact fields of Roundcubes LDAP addressbook. If you are looking for a description how to setup a simple LDAP server as functional backend of RC, see [wiki:Howto_Ldap]. 
    44 
    5 Since RCv0.6 the contact fields of the internal (SQL) addressbook are based on the vcard standard. On the other hand it is possible to use a LDAP server as source of an addressbook. In this case, the question is how to map the contact fields of this two verry different worlds. 
     5Since RCv0.6 the addressbook frontend is based on the vcard standard and the native (SQL) backend is designed to fit the needs of the frontend. On the other hand it is possible to use a LDAP server as addressbook backend as well. In this case, the question is how to map the contact fields of this different worlds. 
    66 
    7 If using a LDAP server the following situations can occur: 
     7If using a LDAP server as RC backend, one of the following situation is possible: 
    88 1. the LDAP server is given and can not be influenced by the users 
    99 2. the LDAP server is under full control of the RC administrator 
     
    1111In situation 1, the contact fields of the LDAP are limited to the set of attributes defined in the schemas of the LDAP server. The topic is just to find a corresponding set of fields on the RC side. 
    1212 
    13 In situation 2, the question is how to find a set of fields that are supported from both, server and all the clients planed to use. If the server will only be used as RC backend, the possbility is to create LDAP schematas such that all the wanted fields are supported. On the other hand, if other clients must be supported as well, the possibilities of them must be considered. 
     13In situation 2, the question is how to find a set of fields that are supported on both sides, server and all the clients planed to use with it. If only RC is planed as frontend client, the possbility is to create LDAP schematas such that all the RC fields are supported. On the other hand, if other clients must be supported, the possibilities of them must be considered as well. 
    1414 
    1515