[horde] Integrating Horde with LDAP, getting there . . .

Spyros Tsiolis stsiol at yahoo.co.uk
Fri Nov 4 18:23:01 UTC 2011


Hello again people,

Well, I managed to make Horde play with LDAP.
Created an LDAP schema and after some bug (mainly
syntax) chasing, I managed to get LDAP contacts
on Horde.

However, I have a problem. Here is the error
message :

<BEGIN

There was an error adding the new contact. Contact your system administrator for further help.
END>

Here's the /etc/openldap/slapd.conf file :

<BEGIN
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#

#
# Global Section
#

include         /etc/openldap/schema/core.schema
include         /etc/openldap/schema/cosine.schema
include         /etc/openldap/schema/inetorgperson.schema
# include               /etc/openldap/schema/nis.schema

#
# Added logging parameters
#

loglevel        296
pidfile         /var/run/openldap/slapd.pid
argsfile        /var/run/openldap/slapd.args
#
# Misc Security Settings
#
# password-hash {SSHA}


# Sample access control policy:
#       Root DSE: allow anyone to read it
#       Subschema (sub)entry DSE: allow anyone to read it
#       Other DSEs:
#               Allow self write access
#               Allow authenticated users read access
#               Allow anonymous users to authenticate
#       Directives needed to implement policy:
# access to dn.base="" by * read
# access to dn.base="cn=Subschema" by * read
# access to *
#       by self write
#       by users read
#       by anonymous auth
#
# if no access controls are present, the default policy
# allows anyone and everyone to read anything but restricts
# updates to rootdn.  (e.g., "access to * by * read")
#
# rootdn can always read and write EVERYTHING!

#######################################################################
# ldbm and/or bdb database definitions
#######################################################################

database        bdb
# suffix                "dc=my-domain,dc=com"
suffix          "dc=abaxb2b,dc=gr"

# rootdn                "cn=manager,dc=my-domain,dc=com"
rootdn          "cn=root,dc=abaxb2b,dc=gr"

# rootpw                {crypt}ijFYNcSNctBYg
rootpw  {SSHA}csQPnPj6uE3qUhw/xzjPO8AU9heQja1z


# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
# directory     /var/lib/ldap
directory       /var/lib/ldap/abaxb2b.gr

#
# Files should be created rw for the owner *only*
#
mode    0600


#
# Indices to maintain for this database
#
index   objectClass     eq
index   cn,sn,mail      eq,sub

#
# db tuning parameters; cache 2,000 entries in memory
#
cachesize       2000


#
# Simple ACL granting access "read" to the world
#
access to *
 by * read
 by * write

END>

I don't enclose the /var/www/horde/turba/conf/sources.php file ,
but I don't think there's anything wrong with that.

Horde versions :

Horde Version

    Horde: 3.3.6

Horde Applications

    Dimp: H3 (1.1.4)
    Horde: 3.3.6
    Imp: H3 (4.3.6) (run Imp tests)
    Ingo: H3 (1.2.3) (run Ingo tests)
    Kronolith: H3 (2.3.3) (run Kronolith tests)
    Mimp: H3 (1.1.3)
    Mnemo: H3 (2.2.3)
    Nag: H3 (2.3.4)
    Turba: H3 (2.3.3) (run Turba tests)

PHP Version

    View phpinfo() screen
    View loaded extensions
    PHP Version: 5.3.1
    PHP Major Version: 5.3
    PHP Minor Version: 1
    PHP Version Classification: release
    This version of PHP has not been fully tested with this version of Horde.


Any help would be greatly appreciated.

TIA,

s.


 

----
"I merely function as a channel that filters 
music through the chaos of noise"
- Vangelis


More information about the horde mailing list