[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: 2.2.11 and --enable-kpasswd

To: Frank Swasey <Frank.Swasey@uvm.edu>
Subject: Re: 2.2.11 and --enable-kpasswd
From: Dan <ml@mutox.org>
Date: Fri, 28 May 2004 01:12:07 +1000
Cc: openldap-software@OpenLDAP.org
In-reply-to: <Pine.WNT.4.58.0405270852250.1848@SOFDL01.pnzchf.nq.hiz.rqh>
References: <1085646383.18809.5.camel@devel2.x32.com.au> <Pine.LNX.4.58.0405270727140.19555@ebova.hiz.rqh> <1085661696.24731.41.camel@devel2.x32.com.au> <Pine.WNT.4.58.0405270852250.1848@SOFDL01.pnzchf.nq.hiz.rqh>

On Thu, 2004-05-27 at 22:53, Frank Swasey wrote:
> Please do not reply to me directly, keep the discussion on
> openldap-software.
> 

Sorry my bad, I hit reply not reply to all.

> 
> NO!  If set up properly, all you need to do is change
> {kerberos}userid@realm into {sasl}userid@realm for the value of the
> userPassword attribute.
> 

>From your previous email i got the impression saslauthd was required for
this. If my saslauthd is configured to use LDAP (as opposed to say
kerberos) how will it be able to verify passwords? Wouldn't this
configuration cause a loop or sorts?

Follow-Ups:
- Re: 2.2.11 and --enable-kpasswd
  - From: Frank Swasey <Frank.Swasey@uvm.edu>

References:
- 2.2.11 and --enable-kpasswd
  - From: Dan <ml@mutox.org>
- Re: 2.2.11 and --enable-kpasswd
  - From: Frank Swasey <Frank.Swasey@uvm.edu>
- Re: 2.2.11 and --enable-kpasswd
  - From: Frank Swasey <Frank.Swasey@uvm.edu>

Prev by Date: RE: 2.2.11 and --enable-kpasswd
Next by Date: Re: Best of SSL / TLS
Index(es):
- Chronological
- Thread