[imp] IMP + LDAP.

[Michael Bull]

At 04:01 PM 19/01/2001 +0100, you wrote:
>Hello all,
>
>I have just downloaded Horde 1.3.3 and IMP 2.3.6 in the hope that I can 
>configure IMP to use LDAP and LDAP only for data/configuration storage.  I 
>heave heard all the arguments about how suitable LDAP is and whether it is 
>fast/slow enough etc. but I prefer to experiment with LDAP alone and then 
>draw my own conclusions!
>
>Here, we are already using our LDAP servers extensively for sendmail 
>routing/PAM authentication/User Profiles/Address books etc.  We already 
>have all the data we need on LDAP and I don't want to have to invent a new 
>method for storing this data (i.e. mySQL etc.)  Can anybody please help me 
>get started on how to configure Horde/IMP to use LDAP exclusively?  The 
>only docs I find appear to be out-of-date... Even just a basic intro.. 
>i.e. which files to edit... how to stucture my arrays to contact the LDAP 
>server etc. would be a great start...

Hi Ray.  I've been starting on this; there are some really good messages on 
this subject between Jon Parise and I on the developers list.   You should 
be able to search the archives off a link on the horde.org site, but if 
you're playing with 2.3, you probably should join the dev@lists.horde.org 
listserv.

One thing we know to expect is that some parts of the IMP LDAP schema 
(which can be found in horde/imp/scripts/db/impPrefsObject.ldap) are out of 
data with the newest preferences; you'll likely need to add to the 
schema.   I'm working on this, but if you get to it first, send the updates 
to the developers listserv so Jon or someone can commit them.

After you've had a look at what's been covered lately about 2.3 and LDAP 
preferences, the dev listserv is a good place to discuss it.

>PS. I'm also getting a problem trying to find Log.php?

You need the latest PEAR code.   Generic/reusable tasks have been 
abstracted to the PEAR library of code.   If you retrieve the PHP code from 
CVS, you can run the install so as to just update the pear component (it 
ends up being placed in a lib/php4/pear directory once installed).


Best of luck,
Mike.