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

Re: LDAP invalid credentials and ldap_sasl_interactive_bind_s

To: Emilio Recio <polywog@navpoint.com>
Subject: Re: LDAP invalid credentials and ldap_sasl_interactive_bind_s
From: David Wright <ichbin@shadlen.org>
Date: Mon, 06 May 2002 18:38:29 -0700
Cc: openldap-software@OpenLDAP.org
References: <1020610790.3519.15.camel@pegasus> <20020505160054.GA7902@boost.horde.net> <3CD72E2E.7040302@navpoint.com>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020502 Debian/1.0rc1-3

Why is SASL enabled by default? It seems that most client/servers out there will (by default esp for anon reads) not use SSL or SASL. Shouldn't it be /off/ by default, and if you want it, turn it on? This is a big point of contention among our IT clients.

Very, very unfortunately, SASL managed to become a part of the LDAP v3 standard.

Follow-Ups:
- Re: LDAP invalid credentials and ldap_sasl_interactive_bind_s
  - From: "Kervin L. Pierre" <kervin@blueprint-tech.com>

References:
- LDAP invalid credentials and ldap_sasl_interactive_bind_s
  - From: Stat <flavio@stat.com.br>
- Re: LDAP invalid credentials and ldap_sasl_interactive_bind_s
  - From: John Morrissey <jwm@horde.net>
- Re: LDAP invalid credentials and ldap_sasl_interactive_bind_s
  - From: Emilio Recio <polywog@navpoint.com>

Prev by Date: Re: LDAP invalid credentials and ldap_sasl_interactive_bind_s
Next by Date: RE: Multiple Objectclass in Backend SQL
Index(es):
- Chronological
- Thread