Hello again:

On 10.04.2012 02:12, Achim wrote:

6. rcmimportreplace ('Replace the entire address book' when importing

a VCF file) does not work for LDAP. The newly imported card is simply added to the existing cards, rather than replacing them all.

I figured out that the implementation for the abstract function delete_all() declared in the base class rcube_addressbook was missing from rcube_ldap. Here is a version that works for me, feel free to add it to the codebase:

 /**
  * Remove all records from the database
  */
 function delete_all() {
     $recursive = true; // to support groups once they work
     return 

$this->_ldap_delete($this->conn,$this->base_dn,$recursive,true); }

     /**
       * helper function from 

http://www.php.net/manual/en/function.ldap-delete.php#21467 */

private function _ldap_delete($ds,$dn,$recursive=false,$root=true){ if($recursive == false){ if (!$root) return(ldap_delete($ds,$dn)); else return true; } else { //searching for sub entries $sr= @ldap_list($ds,$dn,$this->filter ? $this->filter : '(objectclass=*)',array("")); $info = @ldap_get_entries($ds, $sr); $result = false; for($i=0;$i<$info['count'];$i++){ //deleting recursively sub entries

$result=$this->_ldap_delete($ds,$info[$i]['dn'],$recursive,false); } if (!$root) return(ldap_delete($ds,$dn)); else return true; } }

Now there are only 5 issues remaining ;-)

Achim

4. Adding groups under the LDAP directory fails:

[07-Apr-2012 22:40:47 +0200]: C: Connect [calendarserver:389] [Private] [07-Apr-2012 22:40:47 +0200]: S: OK [07-Apr-2012 22:40:47 +0200]: C: Bind [dn: cn=user@hostname.net,ou=private,ou=rcabook,dc=hostname,dc=tld] [pass: XXXXXXXXXXXXX] [07-Apr-2012 22:40:47 +0200]: S: OK [07-Apr-2012 22:40:47 +0200]: C: Add [dn:

cn=Testgroup,cn=user@hostname.net,ou=private,ou=rcabook,dc=hostname,dc=tld]: Array ( [objectClass] => Array ( [0] => top [1] => groupOfNames )

[cn] => Testgroup
[] =>

)

[07-Apr-2012 22:40:47 +0200]: S: Undefined attribute type [07-Apr-2012 22:40:47 +0200]: C: Close

RESULT: Does NOT work, and we get a red error message "An error occured while saving." on top of the web page. Could this be because by default we are using the wrong object classes to create a subgroup?

this is becasue the main.inc.php.dist is not yet compleet, please add in the groups definition array

 'member_attr'  => 'member',   // name of the member attribute, e.g. 

uniqueMember 'name_attr' => 'cn', // attribute to be used as group name

Andreas

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....)

3. 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:

1. Change cn for a contact in jxplorer to "John Doe CN"
2. Search for John Doe CN contact in RC
3. "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!!!

4. 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

5. 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!

7. 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

Hello Alec:

On 10.04.2012 08:12, A.L.E.C wrote:

On 10.04.2012 02:12, Achim wrote:

...

'LDAP_rdn' => 'mail',

'LDAP_rdn' => 'cn' should resolve at least one of your issues.

Correct: thanks for the hint!

...

// does not exist in inetOrgPerson // 'country' => 'c',

'c' is supported in svn-trunk version.

'c' is not supported in the schema inetOrgPerson that I was using in my OpenLDAP installation, so there was no place to store it, and hence the error.

Provide a test account for me.

Will be sent by PM.

Best regards, Achim

Hello Alec:

On 12.04.2012 08:18, A.L.E.C wrote:

...

5. [Able to add jpegPhoto and facsimileTelephoneNumber, but not able

to edit or delete them] Thank you for your suggestion Andreas (mapping phone:workfax or phone:homefax instead of just phone:fax to facsimileTelephoneNumber), but a) the file phone:fax does seems to work, and b) even changing the mapping does not make the field work as expected. Using iOS 5.1, I can add, edit and delete the jpegPhoto field. However, I can also not delete the Fax field with iOS 5.1. Both fields fail in RC with messages like this:

http://trac.roundcube.net/ticket/1488420

Trying to use the trunk version of rcube_ldap.php with 0.7.2 results in a new error when trying to delete the jpegPhoto:

[12-Apr-2012 13:19:21 +0200]: S: OK [12-Apr-2012 13:19:21 +0200]: C: Delete [dn: cn=Contact,cn=user@domain.tld,ou=private,ou=rcabook,dc=domain,dc=tld]: Array( [jpegphoto] => Array ( ..] ) ) [12-Apr-2012 13:19:21 +0200]: S: Inappropriate matching

Whenever this works, would it be possible to use the same "special treatment" for facsimilePhone?

Thanks, Achim

I forgot one thing:

On 12.04.2012 08:18, A.L.E.C wrote:

http://trac.roundcube.net/ticket/1488420

Editing contacts with a jpegPhoto now works by the way: thank you very much!

It is just the photo functionality like editing or removing that still seems broken.

Best regards, Achim

On 12/04/12 12:31, Achim wrote:

Hello f3isar:

On 12.04.2012 11:09, f3isar wrote:

...

I haven't been watching this thread too closely and so I could be wrong but I think some, if not most, of the issues may simply be configuration ones.

Correct, there are now only 2 issues remaining, and they do seem to be code-related.

...

I have a working LDAP config with Round Cube and have no trouble updating or creating records.

I'm happy to share my config if it would be useful

That would be great, so that we can compare with the configuration I posted, and as a result Andreas could perhaps include a "best practice" selection on the wiki page for LDAP?

Best regards, Achim _______________________________________________ Roundcube Users mailing list users@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/users

Here you go, my ldap config:

$rcmail_config['ldap_public']['Private'] = array( 'name' => 'Private Address Book', // Replacement variables supported in host names: // %h - user's IMAP hostname // %n - http hostname ($_SERVER['SERVER_NAME']) // %d - domain (http hostname without the first part) // %z - IMAP domain (IMAP hostname without the first part) // For example %n = mail.domain.tld, %d = domain.tld 'hosts' => array('mail.example.net'), 'port' => 389, 'use_tls' => true, 'ldap_version' => 3, // using LDAPv3 'user_specific' => true, // If true the base_dn, bind_dn and bind_pass default to the user's IMAP login. // %fu - The full username provided, assumes the username is an email // address, uses the username_domain value if not an email address. // %u - The username prior to the '@'. // %d - The domain name after the '@'. // %dc - The domain name hierarchal string e.g. "dc=test,dc=domain,dc=com" // %dn - DN found by ldap search when search_filter/search_base_dn are used 'base_dn' => 'ou=Address Book,cn=%fu,%dc', 'bind_dn' => 'cn=%fu,%dc', 'bind_pass' => '', // It's possible to bind for an individual address book // The login name is used to search for the DN to bind with 'search_base_dn' => '', 'search_filter' => '', // e.g. '(&(objectClass=posixAccount)(uid=%u))' // DN and password to bind as before searching for bind DN, if anonymous search is not allowed 'search_bind_dn' => '', 'search_bind_pw' => '', // Default for %dn variable if search doesn't return DN value 'search_dn_default' => '', // Optional authentication identifier to be used as SASL authorization proxy // bind_dn need to be empty 'auth_cid' => '', // SASL authentication method (for proxy auth), e.g. DIGEST-MD5 'auth_method' => '', // Indicates if the addressbook shall be hidden from the list. // With this option enabled you can still search/view contacts. 'hidden' => false, // Indicates if the addressbook shall not list contacts but only allows searching. 'searchonly' => false, // Indicates if we can write to the LDAP directory or not. // If writable is true then these fields need to be populated: // LDAP_Object_Classes, required_fields, LDAP_rdn 'writable' => true, // To create a new contact these are the object classes to specify // (or any other classes you wish to use). 'LDAP_Object_Classes' => array("top", "person", "inetOrgPerson", "organizationalPerson", "evolutionPerson"), // The RDN field that is used for new entries, this field needs // to be one of the search_fields, the base of base_dn is appended // to the RDN to insert into the LDAP directory. 'LDAP_rdn' => 'cn', // The required fields needed to build a new contact as required by // the object classes (can include additional fields not required by the object classes). 'required_fields' => array("cn", "sn"), 'search_fields' => array('cn'), // mapping of contact fields to directory attributes 'fieldmap' => array( // Roundcube => LDAP

 // Main information
 'firstname'  => 'gn',
 'jobtitle'  => 'businessRole',
 'name'  => 'cn',
 'organization'  => 'o',
 //'photo'  => 'jpegPhoto',
 'prefix'  => 'title',
 'surname'  => 'sn',

 // Contact Properties
 'email'  => 'mail',
 'phone:home'  => 'homePhone',
 'phone:work'  => 'telephoneNumber',
 'phone:mobile'  => 'mobile',
 // Work address
 'address:work'  => 'street',
 //'zipcode:work'  => 'postalCode',
 //'locality:work'  => 'l',
 // Home address
 'address:home'  => 'homePostalAddress',
 //'zipcode:home'  => 'postalAddress',
 //'locality:home'  => 'otherPostalAddress',
 //'region:home'  => 'st',
 //'country:home'  => 'co',
 'website'  => 'labeledURI',

 // Personal information tab
 'anniversary'  =>  'anniversary',
 'birthday'  => 'birthDate',
 'manager'  => 'managerName',
 'spouse'  => 'spouseName',

 // Notes tab
 'notes'  => 'note',

), 'sort' => 'cn', // The field to sort the listing by. 'scope' => 'one', // search mode: sub|base|list 'filter' => '(objectClass=evolutionPerson)', // used for basic listing (if not empty) and will be &'d with search queries. example: status=act 'fuzzy_search' => true, 'vlv' => false, // Enable Virtual List View to more efficiently fetch paginated data (if server supports it) 'numsub_filter' => '(objectClass=organizationalUnit)', // with VLV, we also use numSubOrdinates to query the total number of records. Set this filter to get all numSubOrdinates attributes for counting 'sizelimit' => '0', 'timelimit' => '0', 'referrals' => true|false, // Sets the LDAP_OPT_REFERRALS option. Mostly used in multi-domain Active Directory setups

// definition for contact groups (uncomment if no groups are supported) // for the groups base_dn, the user replacements %fu, %u, $d and %dc work as for base_dn (see above) // if the groups base_dn is empty, the contact base_dn is used for the groups as well // -> in this case, assure that groups and contacts are separated due to the concernig filters! 'groups' => array( 'base_dn' => 'ou=Groups,cn=%fu,%dc', 'filter' => '(objectClass=groupOfNames)', 'object_classes' => array("top", "groupOfNames"), 'member_attr' => 'member', // name of the member attribute, e.g. uniqueMember 'name_attr' => 'cn', // attribute to be used as group name ), );

// An ordered array of the ids of the addressbooks that should be searched // when populating address autocomplete fields server-side. ex: array('sql','Verisign'); $rcmail_config['autocomplete_addressbooks'] = array('Private');

// The minimum number of characters required to be typed in an autocomplete field // before address books will be searched. Most useful for LDAP directories that // may need to do lengthy results building given overly-broad searches $rcmail_config['autocomplete_min_length'] = 3;

// Number of parallel autocomplete requests. // If there's more than one address book, n parallel (async) requests will be created, // where each request will search in one address book. By default (0), all address // books are searched in one request. $rcmail_config['autocomplete_threads'] = 0;

// Max. numer of entries in autocomplete popup. Default: 15. $rcmail_config['autocomplete_max'] = 15;

// show address fields in this order // available placeholders: {street}, {locality}, {zipcode}, {country}, {region} $rcmail_config['address_template'] = '{street}<br/>{locality} {zipcode}<br/>{country} {region}';

// Matching mode for addressbook search (including autocompletion) // 0 - partial (*abc*), default // 1 - strict (abc) // 2 - prefix (abc*) // Note: For LDAP sources fuzzy_search must be enabled to use 'partial' or 'prefix' mode $rcmail_config['addressbook_search_mode'] = 0;