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

Re: separate sasl-secprops for different tansports

To: "Karsten KÃnne" <kuenne@rentec.com>
Subject: Re: separate sasl-secprops for different tansports
From: "Hai Zaar" <haizaar@gmail.com>
Date: Thu, 26 Oct 2006 15:48:38 +0200
Cc: openldap-software@openldap.org
Content-disposition: inline
In-reply-to: <200610260845.52287.kuenne@rentec.com>
References: <cfb54190610260049x56bb1272l370c376aafb05117@mail.gmail.com> <200610260845.52287.kuenne@rentec.com>


Why don't you just remove the SASL mechanisms you don't want? The
SASL/EXTERNAL will always be there

Does not look like that - if I set "sasl-secprops
noanonymous,noplain,noactive" then heimdal-kdc, which uses
SASL/EXTERNAL over slapi fails to connect (removing 'noactive' solves
that).

Karsten.

--
Zaar

Follow-Ups:
- Re: separate sasl-secprops for different tansports
  - From: Howard Chu <hyc@symas.com>
- Re: separate sasl-secprops for different tansports
  - From: Karsten KÃnne <kuenne@rentec.com>
- Re: separate sasl-secprops for different tansports
  - From: Norbert Klasen <norbert@burgundy.dyndns.org>

References:
- separate sasl-secprops for different tansports
  - From: "Hai Zaar" <haizaar@gmail.com>
- Re: separate sasl-secprops for different tansports
  - From: Karsten KÃnne <kuenne@rentec.com>

Prev by Date: Re: separate sasl-secprops for different tansports
Next by Date: Strange behaviour using back-meta + slapo-pcache + glue
Index(es):
- Chronological
- Thread