Independent of this, I believe that the thread "How are you using cn vs displayName?" [0] could be useful to determine the right approach for mapping givenName, sn, cn and displayName.
the today solution is based (as I know) on VCARD... I have never used displayName, are other clients using it?
(my faforite would be just to use 'cn' allways as sum of its parts like givenName, sn and whatever you want as middle name, title and so on....)
- Probably closely related to point 2): changing the content of the
field 'name' => 'cn' fails, i.e. the newly entered information is not stored.
Warning: ldap_mod_replace(): Modify: Naming violation in roundcubemail-0.7.2/program/include/rcube_ldap.php on line 1105
Changing cn using jxplorer 3.2.2 works as expected. How to reproduce:
- Change cn for a contact in jxplorer to "John Doe CN"
- Search for John Doe CN contact in RC
- "John Doe CN" shows up in the "name" field (in accordance with the
fieldmap below): 4) Editing the contact (any field, except cn itself) works perfectly. 5) Search again for same contact. 6) Change cn/name field to "John Doe CNUPDATED" 7) Saving will fail with a "Naming violation" error. From logs/ldap (level 8, which seems to give the same output as level 4 BTW):
[10-Apr-2012 01:51:21 +0200]: C: Replace [dn: cn=John Doe CN,ou=public,ou=rcabook,dc=domain,dc=tld]: Array ( [cn] => John Doe CNUPDATED [sn] => Doe [givenname] => John )
[10-Apr-2012 01:51:21 +0200]: S: Naming violation
here you make a mistake: in RC config you use 'mail' as RDN, but your DN here is [cn=John Doe CN,ou=public,ou=rcabook,dc=domain,dc=tld] thus your RDN must be cn then!!!
- Adding groups under the LDAP directory fails:
as I allready wrote you, add this two lines to the group array and it works 'member_attr' => 'member', // name of the member attribute 'name_attr' => 'cn', // attribute to be used as group name
- Problems with editing and deleting facsimileTelephoneNumber and
jpegPhoto fields
It turns out that 'phone:fax' => 'facsimileTelephoneNumber' works for adding and editing a fax number, but you will not be able to remove or clear an existing one, at least not with the current code:
digging the code in program/steps/addressbook/func.inc I suppose that phone:fax is no RC field, you have to use phone:workfax or phone:homefax
I am using the photo field and you are right, I am not able to delete, but to replace the photo!
- manager, assistant and department fields do not work: manager and
assistant don't show up and cannot be added via "Add field..." at all, while department can be added, but upon saving the new entry the field gets emptied immediately (it appears before submission of the form).
I have never used this fields ...
'street' => 'street', 'zipcode' => 'postalCode', 'locality' => 'l', 'region' => 'st',// does not exist in inetOrgPerson // 'country' => 'c',
you are right. I am using the folloing schema called myperson.schema:
attributetype ( 1.3.6.1.4.1.4203.666.1.95 NAME 'birthday' SUP name ) objectClass ( 1.3.6.1.4.1.4203.666.1.100 NAME 'myPerson' DESC 'Just my own Person' SUP inetOrgPerson STRUCTURAL MAY ( c $ birthday ) )
then it works, but you have to use myPerson then. I planned once to write a WIKI page about this topic, since it is not yet clear how to map all the RC fields to a sensefull LDAP attribute.
please give us feeback about your state now, thanks
Andreas