Changes between Version 6 and Version 7 of Howto_Config_LDAP

Timestamp:

Dec 1, 2011 3:43:19 PM (18 months ago)

Author:

andudi

Comment:

--

Howto_Config_LDAP

@@ -9 +9 @@
 If using a LDAP server as RC backend, one of the following situation is possible:
  1. the LDAP server is given and can not be influenced by the users
- 2. the LDAP server is under full control of the RC administrator
+ 2. the LDAP server is under full control of the RC administrator, beside RC are other clients that must work as well
+ 3. the LDAP server is under full control of the RC administrator, RC is the main client, others can just read some fields
 
-In 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.
+In 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 to find a corresponding set of fields for the RC frontend.
 
-In 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.
+In situation 2, the question is how to find a set of fields that is supported on both sides, server and all the clients planed to use with it. To extend the LDAP schema could be a possibility, but only if the fieldmapping of the other clients can be configured as well as the one of RC can.
+
+In situation 3, when RC is the main client, the possbility is to create LDAP schematas such that all of the RC fields are supported.
+
+Even if this Howto is writen for RC admins in situation 3, it can be usefull in the two other situations as well.
 
 == LDAP Schemas ==