[horde] some trouble adding contacts on turba via openldap

Simon Wilson simon at simonandkate.net
Mon Jul 25 10:03:57 UTC 2016


----- Message from Spyros Tsiolis <stsiol at yahoo.co.uk> ---------
     Date: Mon, 25 Jul 2016 09:32:16 +0000 (UTC)
     From: Spyros Tsiolis <stsiol at yahoo.co.uk>
Reply-To: Spyros Tsiolis <stsiol at yahoo.co.uk>
  Subject: Re: [horde] some trouble adding contacts on turba via openldap
       To: simon at simonandkate.net
       Cc: Horde List <horde at lists.horde.org>


> Hello Simon and apologies for the late reply,
>
>   
> -----------------------------------------------------------------------------------------------
> On Fri, 22/7/16, Simon Wilson <simon at simonandkate.net> wrote:
>
>  Subject: Re: [horde] some trouble adding contacts on turba via openldap
>  To: horde at lists.horde.org
>  Date: Friday, 22 July, 2016, 4:46
>
>
>  I found OpenLDAP
>  quite limiting for back-ending Turba. I got it 
>  working, but ran into issues with multiple
>  email addresses that just 
>  got too
>  difficult to fix, so I shifted my Turba backend to MySQL.
>>  still use OpenLDAP for
>  authentication.
>
>  Having said
>  that, for what it is worth, the schema that I have loaded 
>
>  (that DID work for Turba / OpenLDAP) are
>  (in slapd.conf):
>
>  include
>  /etc/openldap/schema/core.schema
>  include
>  /etc/openldap/schema/cosine.schema
>  include
>  /etc/openldap/schema/inetorgperson.schema
>  include /etc/openldap/schema/nis.schema
>  include /etc/openldap/schema/samba.schema
>  include /etc/openldap/schema/rfc2739.schema
>  include /etc/openldap/schema/horde.schema
>  include /etc/openldap/schema/misc.schema
>
>  You also will need to map the
>  Turba attributes to what OpenLDAP 
>  expects
>  to get - otherwise the write fails.
>
>  Simon
>
>  --
>  Simon Wilson
>   
> -----------------------------------------------------------------------------------------------
>
>
> Well, I am pretty sure I checked the schemas. Everything that should be there
> is there so not much to add there.
> At the moment I have :
>
> /etc/openldap/schema/core.schema
> /etc/openldap/schema/cosine.schema
> /etc/openldap/schema/inetorgperson.schema
> /etc/openldap/schema/horde.schema
> /etc/openldap/schema/misc.schema
>
> Mapping turba attrs to OpenLDAP is already done.
> I suspect you're referring to entries such as
> "mobiletelephonenumber" -> "mobile"
> "homePhone" -> "homePhone" etc.
>
> inside turba/config/backends.php
>
> All that is done and is working properly.
>
> I can even change an existing entry under Turba.
> I _cannot_ ADD a _new_ entry . Turba comes back
> with an error message.
>
> Thank you very much for your kind reply,
>
> Regards,
>
> spyros


----- End message from Spyros Tsiolis <stsiol at yahoo.co.uk> -----

Your LDAP is expecting 'sn'

You need to find out why Turba is not passing it. My backends.local.php has:

'lastname' => 'sn'

along with a bunch of other 'map' parameters for 'localldap'...

(Don't just copy and paste)

'map' => array(
     '__type' => 'turbaType',
     '__members' => 'turbaMembers',
     'firstname' => 'givenName',
     'lastname' => 'sn',
     'middlenames' => 'initials',
     'title' => 'title',
     'company' => 'organizationname',
     'office' => 'roomNumber',
     'department' => 'ou',
     'businessCategory' => 'businesscategory',
     'workAddress' => 'postaladdress',
     'fax' => 'facsimiletelephonenumber',
     'cellPhone' => 'mobile',
     'notes' => 'description',
     'nickname' => 'displayName',
     'spouse' => 'spouseName',
     'website' => 'labeledURI',
     'pgpPublicKey' => 'object_pgppublickey',
     'smimePublicKey' => 'object_smimepublickey',
     'photo' => 'jpegPhoto',
     'freebusyUrl' => 'calFBURL',
);

See 'lastname' is being sent to LDAP as 'sn' which is what your LDAP  
is complaining about.

Simon.

-- 
Simon Wilson
M: 0400 12 11 16
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 1339 bytes
Desc: PGP Public Key
URL: <https://lists.horde.org/archives/horde/attachments/20160725/b1841ab1/attachment-0001.bin>


More information about the horde mailing list