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

Re: [ldapext] Authentication information in LDAP URLs

To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [ldapext] Authentication information in LDAP URLs
From: Michael Ströder <michael@stroeder.com>
Date: Wed, 28 Apr 2004 09:31:13 +0200
Cc: ldapext@ietf.org, ietf-ldapbis@OpenLDAP.org
In-reply-to: <6.0.1.1.0.20040427144615.04a50128@127.0.0.1>
References: <019d01c42910$00172970$1801a8c0@CELLO> <40892F18.7060308@stroeder.com> <20040427112026.GE28861@sverresborg.uninett.no> <6.0.1.1.0.20040427144615.04a50128@127.0.0.1>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Kurt D. Zeilenga wrote:

In note that LDAPBIS had concerns with bindname not be
recognized (let alone supported) by all implementations
and axed it from the revised technical specification.


Uuuh? (Cc:-ed ietf-ldapbis@OpenLDAP.org)

bindname extension should be left in LDAP URL specification since there are existing applications deploying it. web2ldap and various of my custom software are using it based on the ldapurl.LDAPUrl class in python-ldap.

Off course there are security considerations with credentials in LDAP URLs. I generally do not recommend putting credentials in LDAP URLs.

Ciao, Michael.

Follow-Ups:
- Re: [ldapext] Authentication information in LDAP URLs
  - From: Stig Venaas <Stig.Venaas@uninett.no>
- Re: [ldapext] Authentication information in LDAP URLs
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>

Prev by Date: LDAP/BER To LDAP/XML Conversion?
Next by Date: Re: [ldapext] Authentication information in LDAP URLs
Index(es):
- Chronological
- Thread