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

Re: AuthMeth issue summary

To: Mark Wahl <M.Wahl@INNOSOFT.COM>
Subject: Re: AuthMeth issue summary
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
Date: Tue, 07 Dec 1999 13:07:18 -0800
Cc: ietf-ldapext@netscape.com
In-reply-to: <8516.944599939@threadgill.austin.innosoft.com>
References: <"Your message of Mon, 06 Dec 1999 20:55:35 PST." <3.0.5.32.19991206205535.00954490@localhost>
Resent-date: Tue, 07 Dec 1999 13:12:56 -0800 (PST)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"Spw8C.A.mkG.PhXT4"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

AuthMeth draft provides a secure Bind mechanism (DIGEST-MD5)
for authentication users who provide a simple username/password.
Though the mechanism describes how to provide an LDAP DN
authorization identity, it doesn't not allow an LDAP DN
authentication identity (DIGEST-MD5 username) [and it shouldn't].

However, I do believe that we need to provide a secure Bind
mechanism for authentication users who provide an LDAP DN as
their authentication identity.

References:
- AuthMeth issue summary
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
- Re: AuthMeth issue summary
  - From: Mark Wahl <M.Wahl@INNOSOFT.COM>

Prev by Date: Re: AuthMeth issue summary
Next by Date: Re: Authz/Authc state upon start TLS
Index(es):
- Chronological
- Thread