[horde] Re: [imp] ldap logon
Horst Simon
Horst.Simon at oz.quest.com
Mon Nov 11 18:00:45 PST 2002
Hi Alois,
Thanks for your reply, saslauthd is running, and I added "allow bind_vs2"
to the slapd.conf, but I still have the same problem. Are you using
cyrus-imap
and how to you authenticate the logins.
My aim is to use imap login and authenticate to ldap using pam-ldap. This
works
perfect when I connect to the imap server using Netscape or K-Mail, is
starts imapd
and changes to slapd for authentication and back to imapd for conecting to
the mailbox.
If I have imap selected for authentiocation and start the login from imp it
starts up imapd,
but it nevers goes to the ldap server for authentication.
If I select ldap for authenticationg users I get the same result no attempt
is made to authenticate
to ldap. Following is my auth definitions in horde.php. Maybe you might have
some idea.
$conf{'auth']['driver'] = 'ldap';
$conf{'auth']['params']['hostspec'] = 'localhost';
$conf{'auth']['params']['port'] = '389';
$conf{'auth']['params']['basedn'] = 'dc=hsc-consulting,dc=com,dc=au';
$conf{'auth']['params']['uid'] = 'cyrus';
Thanks and Regards,
Horst
"alois blasbichler" <alois.blasbichler at sb-brixen.it> wrote in message
news:1036999722.3dcf5c2a1e552 at titan.sb-brixen.it...
> Zitiere Horst Simon <Horst.Simon at oz.quest.com>:
>
> > Hi,
> >
> > I searched through all the news list, but could not find an answer to
> > my
> > problem. I am using SuSE 8.1, Cyrus-Imap, Postfix, OpenLdap2, Horde 2.1
> > and
> > IMP 3.1.
> >
> > My logon to linux, cyrus are using pam authentication to LDAP, which
> > works.
> > All thhe IMAP clients authenticate to the LDAP directory, except IMP
> > insist
> > on authenticating to the sasldb and not to LDAP, which of course
> > fails.
> >
> > I tried the imap and ldap settings in the horde.conf file but the
> > error
> > messages are still the same in the message log:
> > badlogin: localhost[127.0.0.1] CRAM-MD5 [SASL(-13): user not found: no
> > secret in database]
> > unable to open Berkley db /etc/sasldb2: Invalid argument
> >
> > As mentioned before other IMAP clients authenticate correct.
> >
> > Where do I need to make additional changes in horde/imp to have it
> > authenticate LDAP?
> >
> > Regards,
> > Horst Simon
> >
>
> i had the same problem, then i found in the suse docu in
> /usr/share/doc/packages/cyrus-imapd/README.SUSE :
> ---------------
> Check whether saslauthd is running.
> rcsaslauthd status
> If it is not running, start it with rcsaslauthd start. If you don't want
> to use PAM, edit /etc/sysconfig/saslauthd.
> ---------------------
> do you have toi start the saslauthd - prozess
>
> another suggestion, if ldap gives errormessages:
> ####################
> i am trying for days to install the new horde and imp
> >i use: suse linux 8.1, horde 2.1 and imp 3.1 openldap 2.1.4, kronolith,
> >turba ...
>
> >the autentication i make with pam_ldap and the new imp works fin, but
> >my problem is to store the preferences in LDAP !!! (without ldap its ok)
> >the same error i get with the passwd-module
>
> i have solved the question...
> thanks for the answers,
> it was a ldap-problem the new openldap-DB (v3) dont allow per default
binds
> with old code (code for v2 - DBs)
> seems that the ldap-scripts in horde (ldap.php) are written in the old
code
>
> with the entry "allow bind_v2" in slapd.conf its ok
>
> i am happy, now all works fine
> horde with imp/kronolith/turba is great
> #####################################
> luis
>
>
>
>
>
> --
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>
More information about the horde
mailing list