Skip to main content

LDAP Authentication Password Schema
draft-zeilenga-ldap-authpasswd-05

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3112.
Author Kurt Zeilenga
Last updated 2013-03-02 (Latest revision 2001-02-07)
RFC stream Legacy
Intended RFC status Informational
Formats
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3112 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-zeilenga-ldap-authpasswd-05
A new Request for Comments is now available in online RFC libraries.

        RFC 3112

        Title:      LDAP Authentication Password Schema
        Author(s):  K. Zeilenga
        Status:     Informational
        Date:       May 2001
        Mailbox:    Kurt@OpenLDAP.org
        Pages:      9
        Characters: 17116
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-zeilenga-ldap-authpasswd-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3112.txt

This document describes schema in support of user/password
authentication in a LDAP (Lightweight Directory Access Protocol)
directory including the authPassword attribute type.  This attribute
type holds values derived from the user's password(s) (commonly using
cryptographic strength one-way hash).  authPassword is intended to
used instead of userPassword.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.