Hello Andreas:
On 10.04.2012 22:18, Andreas Dick wrote:
I am using the photo field and you are right, I am not able to delete, but to replace the photo!
I cannot edit a contact that contains a photo at all within RC: none of the fields can be edited, trying to delete the photo gives:
Apr 12 01:40:00 mail slapd[30367]: bdb_modify_internal: delete jpegPhoto Apr 12 01:40:00 mail slapd[30367]: bdb_modify_internal: 18 modify/delete: jpegPhoto: no equality matching rule Apr 12 01:40:00 mail slapd[30367]: hdb_modify: modify failed (18) Apr 12 01:40:00 mail slapd[30367]: send_ldap_result: conn=1013 op=2 p=3 Apr 12 01:40:00 mail slapd[30367]: send_ldap_result: err=18 matched="" text="modify/delete: jpegPhoto: no equality matching rule"
iOS works fine for editing other fields and deleting/replacing the image.
- 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 ...
OK, this is really just a detail for completenes sake, as the fields appear in both RC and inetOrgPerson.
'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 saved the above to /etc/ldap/schema/myperson.schema, added the corresponding include to slapd.conf and restarted the service, but I got:
# service slapd restart Stopping OpenLDAP: slapd. Starting OpenLDAP: slapd - failed: ObjectClassDescription = "(" whsp numericoid whsp ; ObjectClass identifier [ "NAME" qdescrs ] [ "DESC" qdstring ] [ "OBSOLETE" whsp ] [ "SUP" oids ] ; Superior ObjectClasses [ ( "ABSTRACT" / "STRUCTURAL" / "AUXILIARY" ) whsp ] ; default structural [ "MUST" oids ] ; AttributeTypes [ "MAY" oids ] ; AttributeTypes whsp ")"
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.
That would be really helpful, perhaps along with a "perfect" matching for RC to LDAP that uses the most possible compatibility with Outlook and iOS?
Thank you for all your help, Achim