<pre>Network Working Group                                   R. Harrison, Ed.
Request for Comments: 4513                                  Novell, Inc.
Obsoletes: <a href="./rfc2251">2251</a>, <a href="./rfc2829">2829</a>, <a href="./rfc2830">2830</a>                                    June 2006
Category: Standards Track


             <span class="h1">Lightweight Directory Access Protocol (LDAP):</span>
             <span class="h1">Authentication Methods and Security Mechanisms</span>

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This document describes authentication methods and security
   mechanisms of the Lightweight Directory Access Protocol (LDAP).  This
   document details establishment of Transport Layer Security (TLS)
   using the StartTLS operation.

   This document details the simple Bind authentication method including
   anonymous, unauthenticated, and name/password mechanisms and the
   Simple Authentication and Security Layer (SASL) Bind authentication
   method including the EXTERNAL mechanism.

   This document discusses various authentication and authorization
   states through which a session to an LDAP server may pass and the
   actions that trigger these state changes.

   This document, together with other documents in the LDAP Technical
   Specification (see <a href="#section-1">Section 1</a> of the specification's road map),
   obsoletes <a href="./rfc2251">RFC 2251</a>, <a href="./rfc2829">RFC 2829</a>, and <a href="./rfc2830">RFC 2830</a>.











<span class="grey">Harrison                    Standards Track                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
      <a href="#section-1.1">1.1</a>. Relationship to Other Documents ............................<a href="#page-6">6</a>
      <a href="#section-1.2">1.2</a>. Conventions ................................................<a href="#page-6">6</a>
   <a href="#section-2">2</a>. Implementation Requirements .....................................<a href="#page-7">7</a>
   <a href="#section-3">3</a>. StartTLS Operation ..............................................<a href="#page-8">8</a>
      <a href="#section-3.1">3.1</a>.  TLS Establishment Procedures ..............................<a href="#page-8">8</a>
           <a href="#section-3.1.1">3.1.1</a>. StartTLS Request Sequencing .........................<a href="#page-8">8</a>
           <a href="#section-3.1.2">3.1.2</a>. Client Certificate ..................................<a href="#page-9">9</a>
           <a href="#section-3.1.3">3.1.3</a>. Server Identity Check ...............................<a href="#page-9">9</a>
                  <a href="#section-3.1.3.1">3.1.3.1</a>. Comparison of DNS Names ...................<a href="#page-10">10</a>
                  <a href="#section-3.1.3.2">3.1.3.2</a>. Comparison of IP Addresses ................<a href="#page-11">11</a>
                  <a href="#section-3.1.3.3">3.1.3.3</a>. Comparison of Other subjectName Types .....<a href="#page-11">11</a>
           <a href="#section-3.1.4">3.1.4</a>. Discovery of Resultant Security Level ..............<a href="#page-11">11</a>
           <a href="#section-3.1.5">3.1.5</a>. Refresh of Server Capabilities Information .........<a href="#page-11">11</a>
      <a href="#section-3.2">3.2</a>.  Effect of TLS on Authorization State .....................<a href="#page-12">12</a>
      <a href="#section-3.3">3.3</a>. TLS Ciphersuites ..........................................<a href="#page-12">12</a>
   <a href="#section-4">4</a>. Authorization State ............................................<a href="#page-13">13</a>
   <a href="#section-5">5</a>. Bind Operation .................................................<a href="#page-14">14</a>
      <a href="#section-5.1">5.1</a>. Simple Authentication Method ..............................<a href="#page-14">14</a>
           <a href="#section-5.1.1">5.1.1</a>. Anonymous Authentication Mechanism of Simple Bind ..14
           5.1.2. Unauthenticated Authentication Mechanism of
                  Simple Bind ........................................<a href="#page-14">14</a>
           5.1.3. Name/Password Authentication Mechanism of
                  Simple Bind ........................................<a href="#page-15">15</a>
      <a href="#section-5.2">5.2</a>. SASL Authentication Method ................................<a href="#page-16">16</a>
           <a href="#section-5.2.1">5.2.1</a>. SASL Protocol Profile ..............................<a href="#page-16">16</a>
                  <a href="#section-5.2.1.1">5.2.1.1</a>. SASL Service Name for LDAP ................<a href="#page-16">16</a>
                  5.2.1.2. SASL Authentication Initiation and
                           Protocol Exchange .........................<a href="#page-16">16</a>
                  <a href="#section-5.2.1.3">5.2.1.3</a>. Optional Fields ...........................<a href="#page-17">17</a>
                  5.2.1.4. Octet Where Negotiated Security
                           Layers Take Effect ........................<a href="#page-18">18</a>
                  5.2.1.5. Determination of Supported SASL
                           Mechanisms ................................<a href="#page-18">18</a>
                  <a href="#section-5.2.1.6">5.2.1.6</a>. Rules for Using SASL Layers ...............<a href="#page-19">19</a>
                  <a href="#section-5.2.1.7">5.2.1.7</a>. Support for Multiple Authentications ......<a href="#page-19">19</a>
                  <a href="#section-5.2.1.8">5.2.1.8</a>. SASL Authorization Identities .............<a href="#page-19">19</a>
           <a href="#section-5.2.2">5.2.2</a>. SASL Semantics within LDAP .........................<a href="#page-20">20</a>
           <a href="#section-5.2.3">5.2.3</a>. SASL EXTERNAL Authentication Mechanism .............<a href="#page-20">20</a>
                  <a href="#section-5.2.3.1">5.2.3.1</a>. Implicit Assertion ........................<a href="#page-21">21</a>
                  <a href="#section-5.2.3.2">5.2.3.2</a>. Explicit Assertion ........................<a href="#page-21">21</a>
   <a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-21">21</a>
      <a href="#section-6.1">6.1</a>. General LDAP Security Considerations ......................<a href="#page-21">21</a>
      <a href="#section-6.2">6.2</a>. StartTLS Security Considerations ..........................<a href="#page-22">22</a>
      <a href="#section-6.3">6.3</a>. Bind Operation Security Considerations ....................<a href="#page-23">23</a>
           <a href="#section-6.3.1">6.3.1</a>. Unauthenticated Mechanism Security Considerations ..23



<span class="grey">Harrison                    Standards Track                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


           <a href="#section-6.3.2">6.3.2</a>. Name/Password Mechanism Security Considerations ....<a href="#page-23">23</a>
           <a href="#section-6.3.3">6.3.3</a>. Password-Related Security Considerations ...........<a href="#page-23">23</a>
           <a href="#section-6.3.4">6.3.4</a>. Hashed Password Security Considerations ............<a href="#page-24">24</a>
      <a href="#section-6.4">6.4</a>. SASL Security Considerations ..............................<a href="#page-24">24</a>
      <a href="#section-6.5">6.5</a>. Related Security Considerations ...........................<a href="#page-25">25</a>
   <a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-25">25</a>
   <a href="#section-8">8</a>. Acknowledgements ...............................................<a href="#page-25">25</a>
   <a href="#section-9">9</a>. Normative References ...........................................<a href="#page-26">26</a>
   <a href="#section-10">10</a>. Informative References ........................................<a href="#page-27">27</a>
   <a href="#appendix-A">Appendix A</a>. Authentication and Authorization Concepts .............<a href="#page-28">28</a>
      <a href="#appendix-A.1">A.1</a>. Access Control Policy .....................................<a href="#page-28">28</a>
      <a href="#appendix-A.2">A.2</a>. Access Control Factors ....................................<a href="#page-28">28</a>
      <a href="#appendix-A.3">A.3</a>. Authentication, Credentials, Identity .....................<a href="#page-28">28</a>
      <a href="#appendix-A.4">A.4</a>. Authorization Identity ....................................<a href="#page-29">29</a>
   <a href="#appendix-B">Appendix B</a>. Summary of Changes ....................................<a href="#page-29">29</a>
      <a href="#appendix-B.1">B.1</a>. Changes Made to <a href="./rfc2251">RFC 2251</a> ..................................<a href="#page-30">30</a>
           <a href="#appendix-B.1.1">B.1.1</a>. <a href="#section-4.2.1">Section 4.2.1</a> ("Sequencing of the Bind Request") ...<a href="#page-30">30</a>
           B.1.2. <a href="#section-4.2.2">Section 4.2.2</a> ("Authentication and Other Security
                  Services") .........................................<a href="#page-30">30</a>
      <a href="#appendix-B.2">B.2</a>. Changes Made to <a href="./rfc2829">RFC 2829</a> ..................................<a href="#page-30">30</a>
           <a href="#appendix-B.2.1">B.2.1</a>. <a href="#section-4">Section 4</a> ("Required security mechanisms") .........<a href="#page-30">30</a>
           B.2.2. <a href="#section-5.1">Section 5.1</a> ("Anonymous authentication
                  procedure") ........................................<a href="#page-31">31</a>
           <a href="#appendix-B.2.3">B.2.3</a>. <a href="#section-6">Section 6</a> ("Password-based authentication") ........<a href="#page-31">31</a>
           <a href="#appendix-B.2.4">B.2.4</a>. <a href="#section-6.1">Section 6.1</a> ("Digest authentication") ..............<a href="#page-31">31</a>
           B.2.5. <a href="#section-6.2">Section 6.2</a> ("'simple' authentication choice under
                  TLS encryption") ...................................<a href="#page-31">31</a>
           B.2.6. <a href="#section-6.3">Section 6.3</a> ("Other authentication choices with
                  TLS") ..............................................<a href="#page-31">31</a>
           B.2.7. <a href="#section-7.1">Section 7.1</a> ("Certificate-based authentication
                  with TLS") .........................................<a href="#page-31">31</a>
           <a href="#appendix-B.2.8">B.2.8</a>. <a href="#section-8">Section 8</a> ("Other mechanisms") .....................<a href="#page-32">32</a>
           <a href="#appendix-B.2.9">B.2.9</a>. <a href="#section-9">Section 9</a> ("Authorization Identity") ...............<a href="#page-32">32</a>
           <a href="#appendix-B.2.10">B.2.10</a>. <a href="#section-10">Section 10</a> ("TLS Ciphersuites") ...................<a href="#page-32">32</a>
      <a href="#appendix-B.3">B.3</a>. Changes Made to <a href="./rfc2830">RFC 2830</a> ..................................<a href="#page-32">32</a>
           <a href="#appendix-B.3.1">B.3.1</a>. <a href="#section-3.6">Section 3.6</a> ("Server Identity Check") ..............<a href="#page-32">32</a>
           B.3.2. <a href="#section-3.7">Section 3.7</a> ("Refresh of Server Capabilities
                  Information") ......................................<a href="#page-33">33</a>
           B.3.3. <a href="#section-5">Section 5</a> ("Effects of TLS on a Client's
                  Authorization Identity") ...........................<a href="#page-33">33</a>
           <a href="#appendix-B.3.4">B.3.4</a>. <a href="#section-5.2">Section 5.2</a> ("TLS Connection Closure Effects") .....<a href="#page-33">33</a>










<span class="grey">Harrison                    Standards Track                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The Lightweight Directory Access Protocol (LDAP) [<a href="./rfc4510" title="&quot;Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map&quot;">RFC4510</a>] is a
   powerful protocol for accessing directories.  It offers means of
   searching, retrieving, and manipulating directory content and ways to
   access a rich set of security functions.

   It is vital that these security functions be interoperable among all
   LDAP clients and servers on the Internet; therefore there has to be a
   minimum subset of security functions that is common to all
   implementations that claim LDAP conformance.

   Basic threats to an LDAP directory service include (but are not
   limited to):

   (1) Unauthorized access to directory data via data-retrieval
       operations.

   (2) Unauthorized access to directory data by monitoring access of
       others.

   (3) Unauthorized access to reusable client authentication information
       by monitoring access of others.

   (4) Unauthorized modification of directory data.

   (5) Unauthorized modification of configuration information.

   (6) Denial of Service: Use of resources (commonly in excess) in a
       manner intended to deny service to others.

   (7) Spoofing: Tricking a user or client into believing that
       information came from the directory when in fact it did not,
       either by modifying data in transit or misdirecting the client's
       transport connection.  Tricking a user or client into sending
       privileged information to a hostile entity that appears to be the
       directory server but is not.  Tricking a directory server into
       believing that information came from a particular client when in
       fact it came from a hostile entity.

   (8) Hijacking: An attacker seizes control of an established protocol
       session.

   Threats (1), (4), (5), (6), (7), and (8) are active attacks.  Threats
   (2) and (3) are passive attacks.






<span class="grey">Harrison                    Standards Track                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   Threats (1), (4), (5), and (6) are due to hostile clients.  Threats
   (2), (3), (7), and (8) are due to hostile agents on the path between
   client and server or hostile agents posing as a server, e.g., IP
   spoofing.

   LDAP offers the following security mechanisms:

   (1) Authentication by means of the Bind operation.  The Bind
       operation provides a simple method that supports anonymous,
       unauthenticated, and name/password mechanisms, and the Simple
       Authentication and Security Layer (SASL) method, which supports a
       wide variety of authentication mechanisms.

   (2) Mechanisms to support vendor-specific access control facilities
       (LDAP does not offer a standard access control facility).

   (3) Data integrity service by means of security layers in Transport
       Layer Security (TLS) or SASL mechanisms.

   (4) Data confidentiality service by means of security layers in TLS
       or SASL mechanisms.

   (5) Server resource usage limitation by means of administrative
       limits configured on the server.

   (6) Server authentication by means of the TLS protocol or SASL
       mechanisms.

   LDAP may also be protected by means outside the LDAP protocol, e.g.,
   with IP layer security [<a href="./rfc4301" title="&quot;Security Architecture for the Internet Protocol&quot;">RFC4301</a>].

   Experience has shown that simply allowing implementations to pick and
   choose the security mechanisms that will be implemented is not a
   strategy that leads to interoperability.  In the absence of mandates,
   clients will continue to be written that do not support any security
   function supported by the server, or worse, they will only support
   mechanisms that provide inadequate security for most circumstances.

   It is desirable to allow clients to authenticate using a variety of
   mechanisms including mechanisms where identities are represented as
   distinguished names [<a href="#ref-X.501" title="&quot;The Directory: Models&quot;">X.501</a>][RFC4512], in string form [<a href="./rfc4514" title="&quot;Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names&quot;">RFC4514</a>], or as
   used in different systems (e.g., simple user names [<a href="./rfc4013" title="&quot;SASLprep: Stringprep Profile for User Names and Passwords&quot;">RFC4013</a>]).
   Because some authentication mechanisms transmit credentials in plain
   text form, and/or do not provide data security services and/or are
   subject to passive attacks, it is necessary to ensure secure
   interoperability by identifying a mandatory-to-implement mechanism
   for establishing transport-layer security services.




<span class="grey">Harrison                    Standards Track                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   The set of security mechanisms provided in LDAP and described in this
   document is intended to meet the security needs for a wide range of
   deployment scenarios and still provide a high degree of
   interoperability among various LDAP implementations and deployments.

<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>.  Relationship to Other Documents</span>

   This document is an integral part of the LDAP Technical Specification
   [<a href="./rfc4510" title="&quot;Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map&quot;">RFC4510</a>].

   This document, together with [<a href="./rfc4510" title="&quot;Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map&quot;">RFC4510</a>], [<a href="./rfc4511" title="&quot;Lightweight Directory Access Protocol (LDAP): The Protocol&quot;">RFC4511</a>], and [<a href="./rfc4512" title="&quot;Lightweight Directory Access Protocol (LDAP): Directory Information Models&quot;">RFC4512</a>],
   obsoletes <a href="./rfc2251">RFC 2251</a> in its entirety.  Sections <a href="#section-4.2.1">4.2.1</a> (portions) and
   4.2.2 of <a href="./rfc2251">RFC 2251</a> are obsoleted by this document.  <a href="#appendix-B.1">Appendix B.1</a>
   summarizes the substantive changes made to <a href="./rfc2251">RFC 2251</a> by this document.

   This document obsoletes <a href="./rfc2829">RFC 2829</a> in its entirety.  <a href="#appendix-B.2">Appendix B.2</a>
   summarizes the substantive changes made to <a href="./rfc2829">RFC 2829</a> by this document.

   Sections <a href="#section-2">2</a> and <a href="#section-4">4</a> of <a href="./rfc2830">RFC 2830</a> are obsoleted by [<a href="./rfc4511" title="&quot;Lightweight Directory Access Protocol (LDAP): The Protocol&quot;">RFC4511</a>].  The
   remainder of <a href="./rfc2830">RFC 2830</a> is obsoleted by this document.  <a href="#appendix-B.3">Appendix B.3</a>
   summarizes the substantive changes made to <a href="./rfc2830">RFC 2830</a> by this document.

<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>.  Conventions</span>

   The key words "MUST", "MUST NOT", "SHALL", "SHOULD", "SHOULD NOT",
   "MAY", and "OPTIONAL" in this document are to be interpreted as
   described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

   The term "user" represents any human or application entity that is
   accessing the directory using a directory client.  A directory client
   (or client) is also known as a directory user agent (DUA).

   The term "transport connection" refers to the underlying transport
   services used to carry the protocol exchange, as well as associations
   established by these services.

   The term "TLS layer" refers to TLS services used in providing
   security services, as well as associations established by these
   services.

   The term "SASL layer" refers to SASL services used in providing
   security services, as well as associations established by these
   services.

   The term "LDAP message layer" refers to the LDAP Message (PDU)
   services used in providing directory services, as well as
   associations established by these services.




<span class="grey">Harrison                    Standards Track                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   The term "LDAP session" refers to combined services (transport
   connection, TLS layer, SASL layer, LDAP message layer) and their
   associations.

   In general, security terms in this document are used consistently
   with the definitions provided in [<a href="./rfc2828" title="&quot;Internet Security Glossary&quot;">RFC2828</a>].  In addition, several
   terms and concepts relating to security, authentication, and
   authorization are presented in <a href="#appendix-A">Appendix A</a> of this document.  While
   the formal definition of these terms and concepts is outside the
   scope of this document, an understanding of them is prerequisite to
   understanding much of the material in this document.  Readers who are
   unfamiliar with security-related concepts are encouraged to review
   <a href="#appendix-A">Appendix A</a> before reading the remainder of this document.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Implementation Requirements</span>

   LDAP server implementations MUST support the anonymous authentication
   mechanism of the simple Bind method (<a href="#section-5.1.1">Section 5.1.1</a>).

   LDAP implementations that support any authentication mechanism other
   than the anonymous authentication mechanism of the simple Bind method
   MUST support the name/password authentication mechanism of the simple
   Bind method (<a href="#section-5.1.3">Section 5.1.3</a>) and MUST be capable of protecting this
   name/password authentication using TLS as established by the StartTLS
   operation (<a href="#section-3">Section 3</a>).

   Implementations SHOULD disallow the use of the name/password
   authentication mechanism by default when suitable data security
   services are not in place, and they MAY provide other suitable data
   security services for use with this authentication mechanism.

   Implementations MAY support additional authentication mechanisms.
   Some of these mechanisms are discussed below.

   LDAP server implementations SHOULD support client assertion of
   authorization identity via the SASL EXTERNAL mechanism (<a href="#section-5.2.3">Section</a>
   <a href="#section-5.2.3">5.2.3</a>).

   LDAP server implementations that support no authentication mechanism
   other than the anonymous mechanism of the simple bind method SHOULD
   support use of TLS as established by the StartTLS operation (<a href="#section-3">Section</a>
   <a href="#section-3">3</a>).  (Other servers MUST support TLS per the second paragraph of this
   section.)








<span class="grey">Harrison                    Standards Track                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   Implementations supporting TLS MUST support the
   TLS_RSA_WITH_3DES_EDE_CBC_SHA ciphersuite and SHOULD support the
   TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA ciphersuite.  Support for the
   latter ciphersuite is recommended to encourage interoperability with
   implementations conforming to earlier LDAP StartTLS specifications.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  StartTLS Operation</span>

   The Start Transport Layer Security (StartTLS) operation defined in
   <a href="./rfc4511#section-4.14">Section&nbsp;4.14 of [RFC4511]</a> provides the ability to establish TLS
   [<a href="./rfc4346" title="&quot;The TLS Protocol Version 1.1&quot;">RFC4346</a>] in an LDAP session.

   The goals of using the TLS protocol with LDAP are to ensure data
   confidentiality and integrity, and to optionally provide for
   authentication.  TLS expressly provides these capabilities, although
   the authentication services of TLS are available to LDAP only in
   combination with the SASL EXTERNAL authentication method (see <a href="#section-5.2.3">Section</a>
   <a href="#section-5.2.3">5.2.3</a>), and then only if the SASL EXTERNAL implementation chooses to
   make use of the TLS credentials.

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  TLS Establishment Procedures</span>

   This section describes the overall procedures clients and servers
   must follow for TLS establishment.  These procedures take into
   consideration various aspects of the TLS layer including discovery of
   resultant security level and assertion of the client's authorization
   identity.

<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>.  StartTLS Request Sequencing</span>

   A client may send the StartTLS extended request at any time after
   establishing an LDAP session, except:

      - when TLS is currently established on the session,
      - when a multi-stage SASL negotiation is in progress on the
        session, or
      - when there are outstanding responses for operation requests
        previously issued on the session.

   As described in <a href="./rfc4511#section-4.14.1">[RFC4511], Section&nbsp;4.14.1</a>, a (detected) violation of
   any of these requirements results in a return of the operationsError
   resultCode.

   Client implementers should ensure that they strictly follow these
   operation sequencing requirements to prevent interoperability issues.
   Operational experience has shown that violating these requirements





<span class="grey">Harrison                    Standards Track                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   causes interoperability issues because there are race conditions that
   prevent servers from detecting some violations of these requirements
   due to factors such as server hardware speed and network latencies.

   There is no general requirement that the client have or have not
   already performed a Bind operation (<a href="#section-5">Section 5</a>) before sending a
   StartTLS operation request; however, where a client intends to
   perform both a Bind operation and a StartTLS operation, it SHOULD
   first perform the StartTLS operation so that the Bind request and
   response messages are protected by the data security services
   established by the StartTLS operation.

<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>.  Client Certificate</span>

   If an LDAP server requests or demands that a client provide a user
   certificate during TLS negotiation and the client does not present a
   suitable user certificate (e.g., one that can be validated), the
   server may use a local security policy to determine whether to
   successfully complete TLS negotiation.

   If a client that has provided a suitable certificate subsequently
   performs a Bind operation using the SASL EXTERNAL authentication
   mechanism (<a href="#section-5.2.3">Section 5.2.3</a>), information in the certificate may be used
   by the server to identify and authenticate the client.

<span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a>.  Server Identity Check</span>

   In order to prevent man-in-the-middle attacks, the client MUST verify
   the server's identity (as presented in the server's Certificate
   message).  In this section, the client's understanding of the
   server's identity (typically the identity used to establish the
   transport connection) is called the "reference identity".

   The client determines the type (e.g., DNS name or IP address) of the
   reference identity and performs a comparison between the reference
   identity and each subjectAltName value of the corresponding type
   until a match is produced.  Once a match is produced, the server's
   identity has been verified, and the server identity check is
   complete.  Different subjectAltName types are matched in different
   ways.  Sections <a href="#section-3.1.3.1">3.1.3.1</a> - <a href="#section-3.1.3.3">3.1.3.3</a> explain how to compare values of
   various subjectAltName types.

   The client may map the reference identity to a different type prior
   to performing a comparison.  Mappings may be performed for all
   available subjectAltName types to which the reference identity can be
   mapped; however, the reference identity should only be mapped to
   types for which the mapping is either inherently secure (e.g.,
   extracting the DNS name from a URI to compare with a subjectAltName



<span class="grey">Harrison                    Standards Track                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   of type dNSName) or for which the mapping is performed in a secure
   manner (e.g., using DNSSEC, or using user- or admin-configured host-
   to-address/address-to-host lookup tables).

   The server's identity may also be verified by comparing the reference
   identity to the Common Name (CN) [<a href="./rfc4519" title="&quot;Lightweight Directory Access Protocol (LDAP): Schema for User Applications&quot;">RFC4519</a>] value in the leaf Relative
   Distinguished Name (RDN) of the subjectName field of the server's
   certificate.  This comparison is performed using the rules for
   comparison of DNS names in <a href="#section-3.1.3.1">Section 3.1.3.1</a>, below, with the exception
   that no wildcard matching is allowed.  Although the use of the Common
   Name value is existing practice, it is deprecated, and Certification
   Authorities are encouraged to provide subjectAltName values instead.
   Note that the TLS implementation may represent DNs in certificates
   according to X.500 or other conventions.  For example, some X.500
   implementations order the RDNs in a DN using a left-to-right (most
   significant to least significant) convention instead of LDAP's
   right-to-left convention.

   If the server identity check fails, user-oriented clients SHOULD
   either notify the user (clients may give the user the opportunity to
   continue with the LDAP session in this case) or close the transport
   connection and indicate that the server's identity is suspect.
   Automated clients SHOULD close the transport connection and then
   return or log an error indicating that the server's identity is
   suspect or both.

   Beyond the server identity check described in this section, clients
   should be prepared to do further checking to ensure that the server
   is authorized to provide the service it is requested to provide.  The
   client may need to make use of local policy information in making
   this determination.

<span class="h5"><a class="selflink" id="section-3.1.3.1" href="#section-3.1.3.1">3.1.3.1</a>.  Comparison of DNS Names</span>

   If the reference identity is an internationalized domain name,
   conforming implementations MUST convert it to the ASCII Compatible
   Encoding (ACE) format as specified in <a href="./rfc3490#section-4">Section&nbsp;4 of RFC 3490</a> [<a href="./rfc3490" title="&quot;Internationalizing Domain Names in Applications (IDNA)&quot;">RFC3490</a>]
   before comparison with subjectAltName values of type dNSName.
   Specifically, conforming implementations MUST perform the conversion
   operation specified in <a href="./rfc3490#section-4">Section&nbsp;4 of RFC 3490</a> as follows:

      * in step 1, the domain name SHALL be considered a "stored
        string";
      * in step 3, set the flag called "UseSTD3ASCIIRules";
      * in step 4, process each label with the "ToASCII" operation; and
      * in step 5, change all label separators to U+002E (full stop).





<span class="grey">Harrison                    Standards Track                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   After performing the "to-ASCII" conversion, the DNS labels and names
   MUST be compared for equality according to the rules specified in
   <a href="./rfc3490#section-3">Section&nbsp;3 of RFC3490</a>.

   The '*' (ASCII 42) wildcard character is allowed in subjectAltName
   values of type dNSName, and then only as the left-most (least
   significant) DNS label in that value.  This wildcard matches any
   left-most DNS label in the server name.  That is, the subject
   *.example.com matches the server names a.example.com and
   b.example.com, but does not match example.com or a.b.example.com.

<span class="h5"><a class="selflink" id="section-3.1.3.2" href="#section-3.1.3.2">3.1.3.2</a>.  Comparison of IP Addresses</span>

   When the reference identity is an IP address, the identity MUST be
   converted to the "network byte order" octet string representation
   [<a href="./rfc791" title="&quot;Internet Protocol&quot;">RFC791</a>][RFC2460].  For IP Version 4, as specified in <a href="./rfc791">RFC 791</a>, the
   octet string will contain exactly four octets.  For IP Version 6, as
   specified in <a href="./rfc2460">RFC 2460</a>, the octet string will contain exactly sixteen
   octets.  This octet string is then compared against subjectAltName
   values of type iPAddress.  A match occurs if the reference identity
   octet string and value octet strings are identical.

<span class="h5"><a class="selflink" id="section-3.1.3.3" href="#section-3.1.3.3">3.1.3.3</a>.  Comparison of Other subjectName Types</span>

   Client implementations MAY support matching against subjectAltName
   values of other types as described in other documents.

<span class="h4"><a class="selflink" id="section-3.1.4" href="#section-3.1.4">3.1.4</a>.  Discovery of Resultant Security Level</span>

   After a TLS layer is established in an LDAP session, both parties are
   to each independently decide whether or not to continue based on
   local policy and the security level achieved.  If either party
   decides that the security level is inadequate for it to continue, it
   SHOULD remove the TLS layer immediately after the TLS (re)negotiation
   has completed (see <a href="./rfc4511#section-4.14.3">[RFC4511], Section&nbsp;4.14.3</a>, and <a href="#section-3.2">Section 3.2</a> below).
   Implementations may reevaluate the security level at any time and,
   upon finding it inadequate, should remove the TLS layer.

<span class="h4"><a class="selflink" id="section-3.1.5" href="#section-3.1.5">3.1.5</a>.  Refresh of Server Capabilities Information</span>

   After a TLS layer is established in an LDAP session, the client
   SHOULD discard or refresh all information about the server that it
   obtained prior to the initiation of the TLS negotiation and that it
   did not obtain through secure mechanisms.  This protects against
   man-in-the-middle attacks that may have altered any server
   capabilities information retrieved prior to TLS layer installation.





<span class="grey">Harrison                    Standards Track                    [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   The server may advertise different capabilities after installing a
   TLS layer.  In particular, the value of 'supportedSASLMechanisms' may
   be different after a TLS layer has been installed (specifically, the
   EXTERNAL and PLAIN [<a href="#ref-PLAIN" title="&quot;The Plain SASL Mechanism&quot;">PLAIN</a>] mechanisms are likely to be listed only
   after a TLS layer has been installed).

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  Effect of TLS on Authorization State</span>

   The establishment, change, and/or closure of TLS may cause the
   authorization state to move to a new state.  This is discussed
   further in <a href="#section-4">Section 4</a>.

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  TLS Ciphersuites</span>

   Several issues should be considered when selecting TLS ciphersuites
   that are appropriate for use in a given circumstance.  These issues
   include the following:

      - The ciphersuite's ability to provide adequate confidentiality
        protection for passwords and other data sent over the transport
        connection.  Client and server implementers should recognize
        that some TLS ciphersuites provide no confidentiality
        protection, while other ciphersuites that do provide
        confidentiality protection may be vulnerable to being cracked
        using brute force methods, especially in light of ever-
        increasing CPU speeds that reduce the time needed to
        successfully mount such attacks.

      - Client and server implementers should carefully consider the
        value of the password or data being protected versus the level
        of confidentiality protection provided by the ciphersuite to
        ensure that the level of protection afforded by the ciphersuite
        is appropriate.

      - The ciphersuite's vulnerability (or lack thereof) to man-in-the-
        middle attacks.  Ciphersuites vulnerable to man-in-the-middle
        attacks SHOULD NOT be used to protect passwords or sensitive
        data, unless the network configuration is such that the danger
        of a man-in-the-middle attack is negligible.

      - After a TLS negotiation (either initial or subsequent) is
        completed, both protocol peers should independently verify that
        the security services provided by the negotiated ciphersuite are
        adequate for the intended use of the LDAP session.  If they are
        not, the TLS layer should be closed.






<span class="grey">Harrison                    Standards Track                    [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Authorization State</span>

   Every LDAP session has an associated authorization state.  This state
   is comprised of numerous factors such as what (if any) authentication
   state has been established, how it was established, and what security
   services are in place.  Some factors may be determined and/or
   affected by protocol events (e.g., Bind, StartTLS, or TLS closure),
   and some factors may be determined by external events (e.g., time of
   day or server load).

   While it is often convenient to view authorization state in
   simplistic terms (as we often do in this technical specification)
   such as "an anonymous state", it is noted that authorization systems
   in LDAP implementations commonly involve many factors that
   interrelate in complex manners.

   Authorization in LDAP is a local matter.  One of the key factors in
   making authorization decisions is authorization identity.  The Bind
   operation (defined in <a href="./rfc4511#section-4.2">Section&nbsp;4.2 of [RFC4511]</a> and discussed further
   in <a href="#section-5">Section 5</a> below) allows information to be exchanged between the
   client and server to establish an authorization identity for the LDAP
   session.  The Bind operation may also be used to move the LDAP
   session to an anonymous authorization state (see <a href="#section-5.1.1">Section 5.1.1</a>).

   Upon initial establishment of the LDAP session, the session has an
   anonymous authorization identity.  Among other things this implies
   that the client need not send a BindRequest in the first PDU of the
   LDAP message layer.  The client may send any operation request prior
   to performing a Bind operation, and the server MUST treat it as if it
   had been performed after an anonymous Bind operation (<a href="#section-5.1.1">Section 5.1.1</a>).

   Upon receipt of a Bind request, the server immediately moves the
   session to an anonymous authorization state.  If the Bind request is
   successful, the session is moved to the requested authentication
   state with its associated authorization state.  Otherwise, the
   session remains in an anonymous state.

   It is noted that other events both internal and external to LDAP may
   result in the authentication and authorization states being moved to
   an anonymous one.  For instance, the establishment, change, or
   closure of data security services may result in a move to an
   anonymous state, or the user's credential information (e.g.,
   certificate) may have expired.  The former is an example of an event
   internal to LDAP, whereas the latter is an example of an event
   external to LDAP.






<span class="grey">Harrison                    Standards Track                    [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Bind Operation</span>

   The Bind operation (<a href="./rfc4511#section-4.2">[RFC4511], Section&nbsp;4.2</a>) allows authentication
   information to be exchanged between the client and server to
   establish a new authorization state.

   The Bind request typically specifies the desired authentication
   identity.  Some Bind mechanisms also allow the client to specify the
   authorization identity.  If the authorization identity is not
   specified, the server derives it from the authentication identity in
   an implementation-specific manner.

   If the authorization identity is specified, the server MUST verify
   that the client's authentication identity is permitted to assume
   (e.g., proxy for) the asserted authorization identity.  The server
   MUST reject the Bind operation with an invalidCredentials resultCode
   in the Bind response if the client is not so authorized.

<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  Simple Authentication Method</span>

   The simple authentication method of the Bind Operation provides three
   authentication mechanisms:

      - An anonymous authentication mechanism (<a href="#section-5.1.1">Section 5.1.1</a>).

      - An unauthenticated authentication mechanism (<a href="#section-5.1.2">Section 5.1.2</a>).

      - A name/password authentication mechanism using credentials
        consisting of a name (in the form of an LDAP distinguished name
        [<a href="./rfc4514" title="&quot;Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names&quot;">RFC4514</a>]) and a password (<a href="#section-5.1.3">Section 5.1.3</a>).

<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>.  Anonymous Authentication Mechanism of Simple Bind</span>

   An LDAP client may use the anonymous authentication mechanism of the
   simple Bind method to explicitly establish an anonymous authorization
   state by sending a Bind request with a name value of zero length and
   specifying the simple authentication choice containing a password
   value of zero length.

<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>.  Unauthenticated Authentication Mechanism of Simple Bind</span>

   An LDAP client may use the unauthenticated authentication mechanism
   of the simple Bind method to establish an anonymous authorization
   state by sending a Bind request with a name value (a distinguished
   name in LDAP string form [<a href="./rfc4514" title="&quot;Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names&quot;">RFC4514</a>] of non-zero length) and specifying
   the simple authentication choice containing a password value of zero
   length.




<span class="grey">Harrison                    Standards Track                    [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   The distinguished name value provided by the client is intended to be
   used for trace (e.g., logging) purposes only.  The value is not to be
   authenticated or otherwise validated (including verification that the
   DN refers to an existing directory object).  The value is not to be
   used (directly or indirectly) for authorization purposes.

   Unauthenticated Bind operations can have significant security issues
   (see <a href="#section-6.3.1">Section 6.3.1</a>).  In particular, users intending to perform
   Name/Password Authentication may inadvertently provide an empty
   password and thus cause poorly implemented clients to request
   Unauthenticated access.  Clients SHOULD be implemented to require
   user selection of the Unauthenticated Authentication Mechanism by
   means other than user input of an empty password.  Clients SHOULD
   disallow an empty password input to a Name/Password Authentication
   user interface.  Additionally, Servers SHOULD by default fail
   Unauthenticated Bind requests with a resultCode of
   unwillingToPerform.

<span class="h4"><a class="selflink" id="section-5.1.3" href="#section-5.1.3">5.1.3</a>.  Name/Password Authentication Mechanism of Simple Bind</span>

   An LDAP client may use the name/password authentication mechanism of
   the simple Bind method to establish an authenticated authorization
   state by sending a Bind request with a name value (a distinguished
   name in LDAP string form [<a href="./rfc4514" title="&quot;Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names&quot;">RFC4514</a>] of non-zero length) and specifying
   the simple authentication choice containing an OCTET STRING password
   value of non-zero length.

   Servers that map the DN sent in the Bind request to a directory entry
   with an associated set of one or more passwords used with this
   mechanism will compare the presented password to that set of
   passwords.  The presented password is considered valid if it matches
   any member of this set.

   A resultCode of invalidDNSyntax indicates that the DN sent in the
   name value is syntactically invalid.  A resultCode of
   invalidCredentials indicates that the DN is syntactically correct but
   not valid for purposes of authentication, that the password is not
   valid for the DN, or that the server otherwise considers the
   credentials invalid.  A resultCode of success indicates that the
   credentials are valid and that the server is willing to provide
   service to the entity these credentials identify.

   Server behavior is undefined for Bind requests specifying the
   name/password authentication mechanism with a zero-length name value
   and a password value of non-zero length.






<span class="grey">Harrison                    Standards Track                    [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   The name/password authentication mechanism of the simple Bind method
   is not suitable for authentication in environments without
   confidentiality protection.

<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>.  SASL Authentication Method</span>

   The sasl authentication method of the Bind Operation provides
   facilities for using any SASL mechanism including authentication
   mechanisms and other services (e.g., data security services).

<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>.  SASL Protocol Profile</span>

   LDAP allows authentication via any SASL mechanism [<a href="./rfc4422" title="&quot;Simple Authentication and Security Layer (SASL)&quot;">RFC4422</a>].  As LDAP
   includes native anonymous and name/password (plain text)
   authentication methods, the ANONYMOUS [<a href="./rfc4505" title="&quot;The Anonymous SASL Mechanism&quot;">RFC4505</a>] and PLAIN [<a href="#ref-PLAIN" title="&quot;The Plain SASL Mechanism&quot;">PLAIN</a>]
   SASL mechanisms are typically not used with LDAP.

   Each protocol that utilizes SASL services is required to supply
   certain information profiling the way they are exposed through the
   protocol (<a href="./rfc4422#section-4">[RFC4422], Section&nbsp;4</a>).  This section explains how each of
   these profiling requirements is met by LDAP.

<span class="h5"><a class="selflink" id="section-5.2.1.1" href="#section-5.2.1.1">5.2.1.1</a>.  SASL Service Name for LDAP</span>

   The SASL service name for LDAP is "ldap", which has been registered
   with the IANA as a SASL service name.

<span class="h5"><a class="selflink" id="section-5.2.1.2" href="#section-5.2.1.2">5.2.1.2</a>.  SASL Authentication Initiation and Protocol Exchange</span>

   SASL authentication is initiated via a BindRequest message
   (<a href="./rfc4511#section-4.2">[RFC4511], Section&nbsp;4.2</a>) with the following parameters:

      - The version is 3.
      - The AuthenticationChoice is sasl.
      - The mechanism element of the SaslCredentials sequence contains
        the value of the desired SASL mechanism.
      - The optional credentials field of the SaslCredentials sequence
        MAY be used to provide an initial client response for mechanisms
        that are defined to have the client send data first (see
        [<a href="./rfc4422" title="&quot;Simple Authentication and Security Layer (SASL)&quot;">RFC4422</a>], Sections <a href="#section-3">3</a> and <a href="#section-5">5</a>).

   In general, a SASL authentication protocol exchange consists of a
   series of server challenges and client responses, the contents of
   which are specific to and defined by the SASL mechanism.  Thus, for
   some SASL authentication mechanisms, it may be necessary for the
   client to respond to one or more server challenges by sending
   BindRequest messages multiple times.  A challenge is indicated by the
   server sending a BindResponse message with the resultCode set to



<span class="grey">Harrison                    Standards Track                    [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   saslBindInProgress.  This indicates that the server requires the
   client to send a new BindRequest message with the same SASL mechanism
   to continue the authentication process.

   To the LDAP message layer, these challenges and responses are opaque
   binary tokens of arbitrary length.  LDAP servers use the
   serverSaslCreds field (an OCTET STRING) in a BindResponse message to
   transmit each challenge.  LDAP clients use the credentials field (an
   OCTET STRING) in the SaslCredentials sequence of a BindRequest
   message to transmit each response.  Note that unlike some Internet
   protocols where SASL is used, LDAP is not text based and does not
   Base64-transform these challenge and response values.

   Clients sending a BindRequest message with the sasl choice selected
   SHOULD send a zero-length value in the name field.  Servers receiving
   a BindRequest message with the sasl choice selected SHALL ignore any
   value in the name field.

   A client may abort a SASL Bind negotiation by sending a BindRequest
   message with a different value in the mechanism field of
   SaslCredentials or with an AuthenticationChoice other than sasl.

   If the client sends a BindRequest with the sasl mechanism field as an
   empty string, the server MUST return a BindResponse with a resultCode
   of authMethodNotSupported.  This will allow the client to abort a
   negotiation if it wishes to try again with the same SASL mechanism.

   The server indicates completion of the SASL challenge-response
   exchange by responding with a BindResponse in which the resultCode
   value is not saslBindInProgress.

   The serverSaslCreds field in the BindResponse can be used to include
   an optional challenge with a success notification for mechanisms that
   are defined to have the server send additional data along with the
   indication of successful completion.

<span class="h5"><a class="selflink" id="section-5.2.1.3" href="#section-5.2.1.3">5.2.1.3</a>.  Optional Fields</span>

   As discussed above, LDAP provides an optional field for carrying an
   initial response in the message initiating the SASL exchange and
   provides an optional field for carrying additional data in the
   message indicating the outcome of the authentication exchange.  As
   the mechanism-specific content in these fields may be zero length,
   SASL requires protocol specifications to detail how an empty field is
   distinguished from an absent field.






<span class="grey">Harrison                    Standards Track                    [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   Zero-length initial response data is distinguished from no initial
   response data in the initiating message, a BindRequest PDU, by the
   presence of the SaslCredentials.credentials OCTET STRING (of length
   zero) in that PDU.  If the client does not intend to send an initial
   response with the BindRequest initiating the SASL exchange, it MUST
   omit the SaslCredentials.credentials OCTET STRING (rather than
   include an zero-length OCTET STRING).

   Zero-length additional data is distinguished from no additional
   response data in the outcome message, a BindResponse PDU, by the
   presence of the serverSaslCreds OCTET STRING (of length zero) in that
   PDU.  If a server does not intend to send additional data in the
   BindResponse message indicating outcome of the exchange, the server
   SHALL omit the serverSaslCreds OCTET STRING (rather than including a
   zero-length OCTET STRING).

<span class="h5"><a class="selflink" id="section-5.2.1.4" href="#section-5.2.1.4">5.2.1.4</a>.  Octet Where Negotiated Security Layers Take Effect</span>

   SASL layers take effect following the transmission by the server and
   reception by the client of the final BindResponse in the SASL
   exchange with a resultCode of success.

   Once a SASL layer providing data integrity or confidentiality
   services takes effect, the layer remains in effect until a new layer
   is installed (i.e., at the first octet following the final
   BindResponse of the Bind operation that caused the new layer to take
   effect).  Thus, an established SASL layer is not affected by a failed
   or non-SASL Bind.

<span class="h5"><a class="selflink" id="section-5.2.1.5" href="#section-5.2.1.5">5.2.1.5</a>.  Determination of Supported SASL Mechanisms</span>

   Clients may determine the SASL mechanisms a server supports by
   reading the 'supportedSASLMechanisms' attribute from the root DSE
   (DSA-Specific Entry) (<a href="./rfc4512#section-5.1">[RFC4512], Section&nbsp;5.1</a>).  The values of this
   attribute, if any, list the mechanisms the server supports in the
   current LDAP session state.  LDAP servers SHOULD allow all clients --
   even those with an anonymous authorization -- to retrieve the
   'supportedSASLMechanisms' attribute of the root DSE both before and
   after the SASL authentication exchange.  The purpose of the latter is
   to allow the client to detect possible downgrade attacks (see <a href="#section-6.4">Section</a>
   <a href="#section-6.4">6.4</a> and <a href="./rfc4422#section-6.1.2">[RFC4422], Section&nbsp;6.1.2</a>).

   Because SASL mechanisms provide critical security functions, clients
   and servers should be configurable to specify what mechanisms are
   acceptable and allow only those mechanisms to be used.  Both clients
   and servers must confirm that the negotiated security level meets
   their requirements before proceeding to use the session.




<span class="grey">Harrison                    Standards Track                    [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h5"><a class="selflink" id="section-5.2.1.6" href="#section-5.2.1.6">5.2.1.6</a>.  Rules for Using SASL Layers</span>

   Upon installing a SASL layer, the client SHOULD discard or refresh
   all information about the server that it obtained prior to the
   initiation of the SASL negotiation and that it did not obtain through
   secure mechanisms.

   If a lower-level security layer (such as TLS) is installed, any SASL
   layer SHALL be layered on top of such security layers regardless of
   the order of their negotiation.  In all other respects, the SASL
   layer and other security layers act independently, e.g., if both a
   TLS layer and a SASL layer are in effect, then removing the TLS layer
   does not affect the continuing service of the SASL layer.

<span class="h5"><a class="selflink" id="section-5.2.1.7" href="#section-5.2.1.7">5.2.1.7</a>.  Support for Multiple Authentications</span>

   LDAP supports multiple SASL authentications as defined in <a href="./rfc4422#section-4">[RFC4422],
   Section&nbsp;4</a>.

<span class="h5"><a class="selflink" id="section-5.2.1.8" href="#section-5.2.1.8">5.2.1.8</a>.  SASL Authorization Identities</span>

   Some SASL mechanisms allow clients to request a desired authorization
   identity for the LDAP session (<a href="./rfc4422#section-3.4">[RFC4422], Section&nbsp;3.4</a>).  The decision
   to allow or disallow the current authentication identity to have
   access to the requested authorization identity is a matter of local
   policy.  The authorization identity is a string of UTF-8 [<a href="./rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>]
   encoded [<a href="#ref-Unicode" title="&quot;The Unicode Standard, Version 3.2.0&quot;">Unicode</a>] characters corresponding to the following Augmented
   Backus-Naur Form (ABNF) [<a href="./rfc4234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC4234</a>] grammar:

      authzId = dnAuthzId / uAuthzId

      ; distinguished-name-based authz id
      dnAuthzId =  "dn:" distinguishedName

      ; unspecified authorization id, UTF-8 encoded
      uAuthzId = "u:" userid
      userid = *UTF8 ; syntax unspecified

   where the distinguishedName rule is defined in <a href="./rfc4514#section-3">Section&nbsp;3 of [RFC4514]</a>
   and the UTF8 rule is defined in <a href="./rfc4512#section-1.4">Section&nbsp;1.4 of [RFC4512]</a>.

   The dnAuthzId choice is used to assert authorization identities in
   the form of a distinguished name to be matched in accordance with the
   distinguishedNameMatch matching rule (<a href="./rfc4517#section-4.2.15">[RFC4517], Section&nbsp;4.2.15</a>).
   There is no requirement that the asserted distinguishedName value be
   that of an entry in the directory.





<span class="grey">Harrison                    Standards Track                    [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   The uAuthzId choice allows clients to assert an authorization
   identity that is not in distinguished name form.  The format of
   userid is defined only as a sequence of UTF-8 [<a href="./rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>] encoded
   [<a href="#ref-Unicode" title="&quot;The Unicode Standard, Version 3.2.0&quot;">Unicode</a>] characters, and any further interpretation is a local
   matter.  For example, the userid could identify a user of a specific
   directory service, be a login name, or be an email address.  A
   uAuthzId SHOULD NOT be assumed to be globally unique.  To compare
   uAuthzId values, each uAuthzId value MUST be prepared as a "query"
   string (<a href="./rfc3454#section-7">[RFC3454], Section&nbsp;7</a>) using the SASLprep [<a href="./rfc4013" title="&quot;SASLprep: Stringprep Profile for User Names and Passwords&quot;">RFC4013</a>] algorithm,
   and then the two values are compared octet-wise.

   The above grammar is extensible.  The authzId production may be
   extended to support additional forms of identities.  Each form is
   distinguished by its unique prefix (see <a href="./rfc4520#section-3.12">Section&nbsp;3.12 of [RFC4520]</a> for
   registration requirements).

<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>.  SASL Semantics within LDAP</span>

   Implementers must take care to maintain the semantics of SASL
   specifications when handling data that has different semantics in the
   LDAP protocol.

   For example, the SASL DIGEST-MD5 authentication mechanism
   [<a href="#ref-DIGEST-MD5" title="&quot;Using Digest Authentication as a SASL Mechanism&quot;">DIGEST-MD5</a>] utilizes an authentication identity and a realm that are
   syntactically simple strings and semantically simple username
   [<a href="./rfc4013" title="&quot;SASLprep: Stringprep Profile for User Names and Passwords&quot;">RFC4013</a>] and realm values.  These values are not LDAP DNs, and there
   is no requirement that they be represented or treated as such.

<span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>.  SASL EXTERNAL Authentication Mechanism</span>

   A client can use the SASL EXTERNAL (<a href="./rfc4422#appendix-A">[RFC4422], Appendix&nbsp;A</a>) mechanism
   to request the LDAP server to authenticate and establish a resulting
   authorization identity using security credentials exchanged by a
   lower security layer (such as by TLS authentication).  If the
   client's authentication credentials have not been established at a
   lower security layer, the SASL EXTERNAL Bind MUST fail with a
   resultCode of inappropriateAuthentication.  Although this situation
   has the effect of leaving the LDAP session in an anonymous state
   (<a href="#section-4">Section 4</a>), the state of any installed security layer is unaffected.

   A client may either request that its authorization identity be
   automatically derived from its authentication credentials exchanged
   at a lower security layer, or it may explicitly provide a desired
   authorization identity.  The former is known as an implicit
   assertion, and the latter as an explicit assertion.






<span class="grey">Harrison                    Standards Track                    [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h5"><a class="selflink" id="section-5.2.3.1" href="#section-5.2.3.1">5.2.3.1</a>.  Implicit Assertion</span>

   An implicit authorization identity assertion is performed by invoking
   a Bind request of the SASL form using the EXTERNAL mechanism name
   that does not include the optional credentials field (found within
   the SaslCredentials sequence in the BindRequest).  The server will
   derive the client's authorization identity from the authentication
   identity supplied by a security layer (e.g., a public key certificate
   used during TLS layer installation) according to local policy.  The
   underlying mechanics of how this is accomplished are implementation
   specific.

<span class="h5"><a class="selflink" id="section-5.2.3.2" href="#section-5.2.3.2">5.2.3.2</a>.  Explicit Assertion</span>

   An explicit authorization identity assertion is performed by invoking
   a Bind request of the SASL form using the EXTERNAL mechanism name
   that includes the credentials field (found within the SaslCredentials
   sequence in the BindRequest).  The value of the credentials field (an
   OCTET STRING) is the asserted authorization identity and MUST be
   constructed as documented in <a href="#section-5.2.1.8">Section 5.2.1.8</a>.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Security Considerations</span>

   Security issues are discussed throughout this document.  The
   unsurprising conclusion is that security is an integral and necessary
   part of LDAP.  This section discusses a number of LDAP-related
   security considerations.

<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>.  General LDAP Security Considerations</span>

   LDAP itself provides no security or protection from accessing or
   updating the directory by means other than through the LDAP protocol,
   e.g., from inspection of server database files by database
   administrators.

   Sensitive data may be carried in almost any LDAP message, and its
   disclosure may be subject to privacy laws or other legal regulation
   in many countries.  Implementers should take appropriate measures to
   protect sensitive data from disclosure to unauthorized entities.

   A session on which the client has not established data integrity and
   privacy services (e.g., via StartTLS, IPsec, or a suitable SASL
   mechanism) is subject to man-in-the-middle attacks to view and modify
   information in transit.  Client and server implementers SHOULD take
   measures to protect sensitive data in the LDAP session from these
   attacks by using data protection services as discussed in this
   document.  Clients and servers should provide the ability to be
   configured to require these protections.  A resultCode of



<span class="grey">Harrison                    Standards Track                    [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   confidentialityRequired indicates that the server requires
   establishment of (stronger) data confidentiality protection in order
   to perform the requested operation.

   Access control should always be applied when reading sensitive
   information or updating directory information.

   Various security factors, including authentication and authorization
   information and data security services may change during the course
   of the LDAP session, or even during the performance of a particular
   operation.  Implementations should be robust in the handling of
   changing security factors.

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>.  StartTLS Security Considerations</span>

   All security gained via use of the StartTLS operation is gained by
   the use of TLS itself.  The StartTLS operation, on its own, does not
   provide any additional security.

   The level of security provided through the use of TLS depends
   directly on both the quality of the TLS implementation used and the
   style of usage of that implementation.  Additionally, a man-in-the-
   middle attacker can remove the StartTLS extended operation from the
   'supportedExtension' attribute of the root DSE.  Both parties SHOULD
   independently ascertain and consent to the security level achieved
   once TLS is established and before beginning use of the TLS-
   protected session.  For example, the security level of the TLS layer
   might have been negotiated down to plaintext.

   Clients MUST either warn the user when the security level achieved
   does not provide an acceptable level of data confidentiality and/or
   data integrity protection, or be configurable to refuse to proceed
   without an acceptable level of security.

   As stated in <a href="#section-3.1.2">Section 3.1.2</a>, a server may use a local security policy
   to determine whether to successfully complete TLS negotiation.
   Information in the user's certificate that is originated or verified
   by the certification authority should be used by the policy
   administrator when configuring the identification and authorization
   policy.

   Server implementers SHOULD allow server administrators to elect
   whether and when data confidentiality and integrity are required, as
   well as elect whether authentication of the client during the TLS
   handshake is required.

   Implementers should be aware of and understand TLS security
   considerations as discussed in the TLS specification [<a href="./rfc4346" title="&quot;The TLS Protocol Version 1.1&quot;">RFC4346</a>].



<span class="grey">Harrison                    Standards Track                    [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>.  Bind Operation Security Considerations</span>

   This section discusses several security considerations relevant to
   LDAP authentication via the Bind operation.

<span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>.  Unauthenticated Mechanism Security Considerations</span>

   Operational experience shows that clients can (and frequently do)
   misuse the unauthenticated authentication mechanism of the simple
   Bind method (see <a href="#section-5.1.2">Section 5.1.2</a>).  For example, a client program might
   make a decision to grant access to non-directory information on the
   basis of successfully completing a Bind operation.  LDAP server
   implementations may return a success response to an unauthenticated
   Bind request.  This may erroneously leave the client with the
   impression that the server has successfully authenticated the
   identity represented by the distinguished name when in reality, an
   anonymous authorization state has been established.  Clients that use
   the results from a simple Bind operation to make authorization
   decisions should actively detect unauthenticated Bind requests (by
   verifying that the supplied password is not empty) and react
   appropriately.

<span class="h4"><a class="selflink" id="section-6.3.2" href="#section-6.3.2">6.3.2</a>.  Name/Password Mechanism Security Considerations</span>

   The name/password authentication mechanism of the simple Bind method
   discloses the password to the server, which is an inherent security
   risk.  There are other mechanisms, such as SASL DIGEST-MD5
   [<a href="#ref-DIGEST-MD5" title="&quot;Using Digest Authentication as a SASL Mechanism&quot;">DIGEST-MD5</a>], that do not disclose the password to the server.

<span class="h4"><a class="selflink" id="section-6.3.3" href="#section-6.3.3">6.3.3</a>.  Password-Related Security Considerations</span>

   LDAP allows multi-valued password attributes.  In systems where
   entries are expected to have one and only one password,
   administrative controls should be provided to enforce this behavior.

   The use of clear text passwords and other unprotected authentication
   credentials is strongly discouraged over open networks when the
   underlying transport service cannot guarantee confidentiality.  LDAP
   implementations SHOULD NOT by default support authentication methods
   using clear text passwords and other unprotected authentication
   credentials unless the data on the session is protected using TLS or
   other data confidentiality and data integrity protection.

   The transmission of passwords in the clear -- typically for
   authentication or modification -- poses a significant security risk.
   This risk can be avoided by using SASL authentication [<a href="./rfc4422" title="&quot;Simple Authentication and Security Layer (SASL)&quot;">RFC4422</a>]





<span class="grey">Harrison                    Standards Track                    [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   mechanisms that do not transmit passwords in the clear or by
   negotiating transport or session layer data confidentiality services
   before transmitting password values.

   To mitigate the security risks associated with the transfer of
   passwords, a server implementation that supports any password-based
   authentication mechanism that transmits passwords in the clear MUST
   support a policy mechanism that at the time of authentication or
   password modification, requires that:

         A TLS layer has been successfully installed.

         OR

         Some other data confidentiality mechanism that protects the
         password value from eavesdropping has been provided.

         OR

         The server returns a resultCode of confidentialityRequired for
         the operation (i.e., name/password Bind with password value,
         SASL Bind transmitting a password value in the clear, add or
         modify including a userPassword value, etc.), even if the
         password value is correct.

   Server implementations may also want to provide policy mechanisms to
   invalidate or otherwise protect accounts in situations where a server
   detects that a password for an account has been transmitted in the
   clear.

<span class="h4"><a class="selflink" id="section-6.3.4" href="#section-6.3.4">6.3.4</a>.  Hashed Password Security Considerations</span>

   Some authentication mechanisms (e.g., DIGEST-MD5) transmit a hash of
   the password value that may be vulnerable to offline dictionary
   attacks.  Implementers should take care to protect such hashed
   password values during transmission using TLS or other
   confidentiality mechanisms.

<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>.  SASL Security Considerations</span>

   Until data integrity service is installed on an LDAP session, an
   attacker can modify the transmitted values of the
   'supportedSASLMechanisms' attribute response and thus downgrade the
   list of available SASL mechanisms to include only the least secure
   mechanism.  To detect this type of attack, the client may retrieve
   the SASL mechanisms the server makes available both before and after
   data integrity service is installed on an LDAP session.  If the
   client finds that the integrity-protected list (the list obtained



<span class="grey">Harrison                    Standards Track                    [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   after data integrity service was installed) contains a stronger
   mechanism than those in the previously obtained list, the client
   should assume the previously obtained list was modified by an
   attacker.  In this circumstance it is recommended that the client
   close the underlying transport connection and then reconnect to
   reestablish the session.

<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>.  Related Security Considerations</span>

   Additional security considerations relating to the various
   authentication methods and mechanisms discussed in this document
   apply and can be found in [<a href="./rfc4422" title="&quot;Simple Authentication and Security Layer (SASL)&quot;">RFC4422</a>], [<a href="./rfc4013" title="&quot;SASLprep: Stringprep Profile for User Names and Passwords&quot;">RFC4013</a>], [<a href="./rfc3454" title="&quot;Preparation of Internationalized Strings (&quot;">RFC3454</a>], and
   [<a href="./rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>].

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  IANA Considerations</span>

   The IANA has updated the LDAP Protocol Mechanism registry to indicate
   that this document and [<a href="./rfc4511" title="&quot;Lightweight Directory Access Protocol (LDAP): The Protocol&quot;">RFC4511</a>] provide the definitive technical
   specification for the StartTLS (1.3.6.1.4.1.1466.20037) extended
   operation.

   The IANA has updated the LDAP LDAPMessage types registry to indicate
   that this document and [<a href="./rfc4511" title="&quot;Lightweight Directory Access Protocol (LDAP): The Protocol&quot;">RFC4511</a>] provide the definitive technical
   specification for the bindRequest (0) and bindResponse (1) message
   types.

   The IANA has updated the LDAP Bind Authentication Method registry to
   indicate that this document and [<a href="./rfc4511" title="&quot;Lightweight Directory Access Protocol (LDAP): The Protocol&quot;">RFC4511</a>] provide the definitive
   technical specification for the simple (0) and sasl (3) bind
   authentication methods.

   The IANA has updated the LDAP authzid prefixes registry to indicate
   that this document provides the definitive technical specification
   for the dnAuthzId (dn:) and uAuthzId (u:) authzid prefixes.

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  Acknowledgements</span>

   This document combines information originally contained in <a href="./rfc2251">RFC 2251</a>,
   <a href="./rfc2829">RFC 2829</a>, and <a href="./rfc2830">RFC 2830</a>.  <a href="./rfc2251">RFC 2251</a> was a product of the Access,
   Searching, and Indexing of Directories (ASID) Working Group.  <a href="./rfc2829">RFC</a>
   <a href="./rfc2829">2829</a> and <a href="./rfc2830">RFC 2830</a> were products of the LDAP Extensions (LDAPEXT)
   Working Group.

   This document is a product of the IETF LDAP Revision (LDAPBIS)
   working group.






<span class="grey">Harrison                    Standards Track                    [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  Normative References</span>

   [<a id="ref-RFC791">RFC791</a>]     Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>,
                September 1981.

   [<a id="ref-RFC2119">RFC2119</a>]    Bradner, S., "Key words for use in RFCs to Indicate
                Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC2460">RFC2460</a>]    Deering, S. and R. Hinden, "Internet Protocol, Version 6
                (IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998.

   [<a id="ref-RFC3454">RFC3454</a>]    Hoffman, P. and M. Blanchet, "Preparation of
                Internationalized Strings ("stringprep")", <a href="./rfc3454">RFC 3454</a>,
                December 2002.

   [<a id="ref-RFC3490">RFC3490</a>]    Faltstrom, P., Hoffman, P., and A. Costello,
                "Internationalizing Domain Names in Applications
                (IDNA)", <a href="./rfc3490">RFC 3490</a>, March 2003.

   [<a id="ref-RFC3629">RFC3629</a>]    Yergeau, F., "UTF-8, a transformation format of ISO
                10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.

   [<a id="ref-RFC4013">RFC4013</a>]    Zeilenga, K., "SASLprep: Stringprep Profile for User
                Names and Passwords", <a href="./rfc4013">RFC 4013</a>, February 2005.

   [<a id="ref-RFC4234">RFC4234</a>]    Crocker, D. and P. Overell, "Augmented BNF for Syntax
                Specifications: ABNF", <a href="./rfc4234">RFC 4234</a>, October 2005.

   [<a id="ref-RFC4346">RFC4346</a>]    Dierks, T. and E. Rescorla, "The TLS Protocol Version
                1.1", <a href="./rfc4346">RFC 4346</a>, March 2006.

   [<a id="ref-RFC4422">RFC4422</a>]    Melnikov, A., Ed. and K. Zeilenga, Ed., "Simple
                Authentication and Security Layer (SASL)", <a href="./rfc4422">RFC 4422</a>,
                June 2006.

   [<a id="ref-RFC4510">RFC4510</a>]    Zeilenga, K., Ed., "Lightweight Directory Access
                Protocol (LDAP): Technical Specification Road Map", <a href="./rfc4510">RFC</a>
                <a href="./rfc4510">4510</a>, June 2006.

   [<a id="ref-RFC4511">RFC4511</a>]    Sermersheim, J., Ed., "Lightweight Directory Access
                Protocol (LDAP): The Protocol", <a href="./rfc4511">RFC 4511</a>, June 2006.

   [<a id="ref-RFC4512">RFC4512</a>]    Zeilenga, K., "Lightweight Directory Access Protocol
                (LDAP): Directory Information Models", <a href="./rfc4512">RFC 4512</a>, June
                2006.






<span class="grey">Harrison                    Standards Track                    [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   [<a id="ref-RFC4514">RFC4514</a>]    Zeilenga, K., Ed., "Lightweight Directory Access
                Protocol (LDAP): String Representation of Distinguished
                Names", <a href="./rfc4514">RFC 4514</a>, June 2006.

   [<a id="ref-RFC4517">RFC4517</a>]    Legg, S., Ed., "Lightweight Directory Access Protocol
                (LDAP): Syntaxes and Matching Rules", <a href="./rfc4517">RFC 4517</a>, June
                2006.

   [<a id="ref-RFC4519">RFC4519</a>]    Sciberras, A., Ed., "Lightweight Directory Access
                Protocol (LDAP): Schema for User Applications", <a href="./rfc4519">RFC</a>
                <a href="./rfc4519">4519</a>, June 2006.

   [<a id="ref-RFC4520">RFC4520</a>]    Zeilenga, K., "Internet Assigned Numbers Authority
                (IANA) Considerations for the Lightweight Directory
                Access Protocol (LDAP)", <a href="https://www.rfc-editor.org/bcp/bcp64">BCP 64</a>, <a href="./rfc4520">RFC 4520</a>, June 2006.

   [<a id="ref-Unicode">Unicode</a>]    The Unicode Consortium, "The Unicode Standard, Version
                3.2.0" is defined by "The Unicode Standard, Version 3.0"
                (Reading, MA, Addison-Wesley, 2000.  ISBN 0-201-61633-
                5), as amended by the "Unicode Standard Annex #27:
                Unicode 3.1" (<a href="http://www.unicode.org/reports/tr27/">http://www.unicode.org/reports/tr27/</a>) and
                by the "Unicode Standard Annex #28: Unicode 3.2"
                (<a href="http://www.unicode.org/reports/tr28/">http://www.unicode.org/reports/tr28/</a>).

   [<a id="ref-X.501">X.501</a>]      ITU-T Rec. X.501, "The Directory: Models", 1993.

<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  Informative References</span>

   [<a id="ref-DIGEST-MD5">DIGEST-MD5</a>] Leach, P., Newman, C., and A. Melnikov, "Using Digest
                Authentication as a SASL Mechanism", Work in Progress,
                March 2006.

   [<a id="ref-PLAIN">PLAIN</a>]      Zeilenga, K., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22The+Plain+SASL+Mechanism%22'>"The Plain SASL Mechanism"</a>, Work in
                Progress, March 2005.

   [<a id="ref-RFC2828">RFC2828</a>]    Shirey, R., "Internet Security Glossary", FYI 36, <a href="./rfc2828">RFC</a>
                <a href="./rfc2828">2828</a>, May 2000.

   [<a id="ref-RFC4301">RFC4301</a>]    Kent, S. and K. Seo, "Security Architecture for the
                Internet Protocol", <a href="./rfc4301">RFC 4301</a>, December 2005.

   [<a id="ref-RFC4505">RFC4505</a>]    Zeilenga, K., "The Anonymous SASL Mechanism", <a href="./rfc4505">RFC 4505</a>,
                June 2006.








<span class="grey">Harrison                    Standards Track                    [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  Authentication and Authorization Concepts</span>

   This appendix is non-normative.

   This appendix defines basic terms, concepts, and interrelationships
   regarding authentication, authorization, credentials, and identity.
   These concepts are used in describing how various security approaches
   are utilized in client authentication and authorization.

<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>.  Access Control Policy</span>

   An access control policy is a set of rules defining the protection of
   resources, generally in terms of the capabilities of persons or other
   entities accessing those resources.  Security objects and mechanisms,
   such as those described here, enable the expression of access control
   policies and their enforcement.

<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>.  Access Control Factors</span>

   A request, when it is being processed by a server, may be associated
   with a wide variety of security-related factors.  The server uses
   these factors to determine whether and how to process the request.
   These are called access control factors (ACFs).  They might include
   source IP address, encryption strength, the type of operation being
   requested, time of day, etc..  Some factors may be specific to the
   request itself; others may be associated with the transport
   connection via which the request is transmitted; and others (e.g.,
   time of day) may be "environmental".

   Access control policies are expressed in terms of access control
   factors; for example, "a request having ACFs i,j,k can perform
   operation Y on resource Z".  The set of ACFs that a server makes
   available for such expressions is implementation specific.

<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>.  Authentication, Credentials, Identity</span>

   Authentication credentials are the evidence supplied by one party to
   another, asserting the identity of the supplying party (e.g., a user)
   who is attempting to establish a new authorization state with the
   other party (typically a server).  Authentication is the process of
   generating, transmitting, and verifying these credentials and thus
   the identity they assert.  An authentication identity is the name
   presented in a credential.

   There are many forms of authentication credentials.  The form used
   depends upon the particular authentication mechanism negotiated by
   the parties.  X.509 certificates, Kerberos tickets, and simple
   identity and password pairs are all examples of authentication



<span class="grey">Harrison                    Standards Track                    [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   credential forms.  Note that an authentication mechanism may
   constrain the form of authentication identities used with it.

<span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a>.  Authorization Identity</span>

   An authorization identity is one kind of access control factor.  It
   is the name of the user or other entity that requests that operations
   be performed.  Access control policies are often expressed in terms
   of authorization identities; for example, "entity X can perform
   operation Y on resource Z".

   The authorization identity of an LDAP session is often semantically
   the same as the authentication identity presented by the client, but
   it may be different.  SASL allows clients to specify an authorization
   identity distinct from the authentication identity asserted by the
   client's credentials.  This permits agents such as proxy servers to
   authenticate using their own credentials, yet request the access
   privileges of the identity for which they are proxying [<a href="./rfc4422" title="&quot;Simple Authentication and Security Layer (SASL)&quot;">RFC4422</a>].
   Also, the form of authentication identity supplied by a service like
   TLS may not correspond to the authorization identities used to
   express a server's access control policy, thus requiring a server-
   specific mapping to be done.  The method by which a server composes
   and validates an authorization identity from the authentication
   credentials supplied by a client is implementation specific.

<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>.  Summary of Changes</span>

   This appendix is non-normative.

   This appendix summarizes substantive changes made to <a href="./rfc2251">RFC 2251</a>, <a href="./rfc2829">RFC</a>
   <a href="./rfc2829">2829</a> and <a href="./rfc2830">RFC 2830</a>.  In addition to the specific changes detailed
   below, the reader of this document should be aware that numerous
   general editorial changes have been made to the original content from
   the source documents.  These changes include the following:

   - The material originally found in <a href="./rfc2251">RFC 2251</a> Sections <a href="#section-4.2.1">4.2.1</a> and <a href="#section-4.2.2">4.2.2</a>,
     <a href="./rfc2829">RFC 2829</a> (all sections except Sections <a href="#section-2">2</a> and <a href="#section-4">4</a>), and <a href="./rfc2830">RFC 2830</a> was
     combined into a single document.

   - The combined material was substantially reorganized and edited to
     group related subjects, improve the document flow, and clarify
     intent.

   - Changes were made throughout the text to align with definitions of
     LDAP protocol layers and IETF security terminology.






<span class="grey">Harrison                    Standards Track                    [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


   - Substantial updates and additions were made to security
     considerations from both documents based on current operational
     experience.

<span class="h3"><a class="selflink" id="appendix-B.1" href="#appendix-B.1">B.1</a>.  Changes Made to <a href="./rfc2251">RFC 2251</a></span>

   This section summarizes the substantive changes made to Sections
   4.2.1 and 4.2.2 of <a href="./rfc2251">RFC 2251</a> by this document.  Additional substantive
   changes to <a href="./rfc2251#section-4.2.1">Section&nbsp;4.2.1 of RFC 2251</a> are also documented in
   [<a href="./rfc4511" title="&quot;Lightweight Directory Access Protocol (LDAP): The Protocol&quot;">RFC4511</a>].

<span class="h4"><a class="selflink" id="appendix-B.1.1" href="#appendix-B.1.1">B.1.1</a>.  <a href="#section-4.2.1">Section 4.2.1</a> ("Sequencing of the Bind Request")</span>

   - Paragraph 1: Removed the sentence, "If at any stage the client
     wishes to abort the bind process it MAY unbind and then drop the
     underlying connection".  The Unbind operation still permits this
     behavior, but it is not documented explicitly.

   - Clarified that the session is moved to an anonymous state upon
     receipt of the BindRequest PDU and that it is only moved to a non-
     anonymous state if and when the Bind request is successful.

<span class="h4"><a class="selflink" id="appendix-B.1.2" href="#appendix-B.1.2">B.1.2</a>.  <a href="#section-4.2.2">Section 4.2.2</a> ("Authentication and Other Security Services")</span>

   - <a href="./rfc2251">RFC 2251</a> states that anonymous authentication MUST be performed
     using the simple bind method.  This specification defines the
     anonymous authentication mechanism of the simple bind method and
     requires all conforming implementations to support it.  Other
     authentication mechanisms producing anonymous authentication and
     authorization state may also be implemented and used by conforming
     implementations.

<span class="h3"><a class="selflink" id="appendix-B.2" href="#appendix-B.2">B.2</a>.  Changes Made to <a href="./rfc2829">RFC 2829</a></span>

   This section summarizes the substantive changes made to <a href="./rfc2829">RFC 2829</a>.

<span class="h4"><a class="selflink" id="appendix-B.2.1" href="#appendix-B.2.1">B.2.1</a>.  <a href="#section-4">Section 4</a> ("Required security mechanisms")</span>

   - The name/password authentication mechanism (see Section B.2.5
     below) protected by TLS replaces the SASL DIGEST-MD5 mechanism as
     LDAP's mandatory-to-implement password-based authentication
     mechanism.  Implementations are encouraged to continue supporting
     SASL DIGEST-MD5 [<a href="#ref-DIGEST-MD5" title="&quot;Using Digest Authentication as a SASL Mechanism&quot;">DIGEST-MD5</a>].








<span class="grey">Harrison                    Standards Track                    [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h4"><a class="selflink" id="appendix-B.2.2" href="#appendix-B.2.2">B.2.2</a>.  <a href="#section-5.1">Section 5.1</a> ("Anonymous authentication procedure")</span>

   - Clarified that anonymous authentication involves a name value of
     zero length and a password value of zero length.  The
     unauthenticated authentication mechanism was added to handle simple
     Bind requests involving a name value with a non-zero length and a
     password value of zero length.

<span class="h4"><a class="selflink" id="appendix-B.2.3" href="#appendix-B.2.3">B.2.3</a>.  <a href="#section-6">Section 6</a> ("Password-based authentication")</span>

   - See Section B.2.1.

<span class="h4"><a class="selflink" id="appendix-B.2.4" href="#appendix-B.2.4">B.2.4</a>.  <a href="#section-6.1">Section 6.1</a> ("Digest authentication")</span>

   - As the SASL-DIGEST-MD5 mechanism is no longer mandatory to
     implement, this section is now historical and was not included in
     this document.  <a href="./rfc2829#section-6.1">RFC 2829, Section&nbsp;6.1</a>, continues to document the
     SASL DIGEST-MD5 authentication mechanism.

<span class="h4"><a class="selflink" id="appendix-B.2.5" href="#appendix-B.2.5">B.2.5</a>.  <a href="#section-6.2">Section 6.2</a> ("'simple' authentication choice under TLS</span>
        encryption")

   - Renamed the "simple" authentication mechanism to the name/password
     authentication mechanism to better describe it.

   - The use of TLS was generalized to align with definitions of LDAP
     protocol layers.  TLS establishment is now discussed as an
     independent subject and is generalized for use with all
     authentication mechanisms and other security layers.

   - Removed the implication that the userPassword attribute is the sole
     location for storage of password values to be used in
     authentication.  There is no longer any implied requirement for how
     or where passwords are stored at the server for use in
     authentication.

<span class="h4"><a class="selflink" id="appendix-B.2.6" href="#appendix-B.2.6">B.2.6</a>.  <a href="#section-6.3">Section 6.3</a> ("Other authentication choices with TLS")</span>

   - See Section B.2.5.

<span class="h4"><a class="selflink" id="appendix-B.2.7" href="#appendix-B.2.7">B.2.7</a>.  <a href="#section-7.1">Section 7.1</a> ("Certificate-based authentication with TLS")</span>

   - See Section B.2.5.








<span class="grey">Harrison                    Standards Track                    [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h4"><a class="selflink" id="appendix-B.2.8" href="#appendix-B.2.8">B.2.8</a>.  <a href="#section-8">Section 8</a> ("Other mechanisms")</span>

   - All SASL authentication mechanisms are explicitly allowed within
     LDAP.  Specifically, this means the SASL ANONYMOUS and SASL PLAIN
     mechanisms are no longer precluded from use within LDAP.

<span class="h4"><a class="selflink" id="appendix-B.2.9" href="#appendix-B.2.9">B.2.9</a>.  <a href="#section-9">Section 9</a> ("Authorization Identity")</span>

   - Specified matching rules for dnAuthzId and uAuthzId values.  In
     particular, the DN value in the dnAuthzId form must be matched
     using DN matching rules, and the uAuthzId value MUST be prepared
     using SASLprep rules before being compared octet-wise.

   - Clarified that uAuthzId values should not be assumed to be globally
     unique.

<span class="h4"><a class="selflink" id="appendix-B.2.10" href="#appendix-B.2.10">B.2.10</a>.  <a href="#section-10">Section 10</a> ("TLS Ciphersuites")</span>

   - TLS ciphersuite recommendations are no longer included in this
     specification.  Implementations must now support the
     TLS_RSA_WITH_3DES_EDE_CBC_SHA ciphersuite and should continue to
     support the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA ciphersuite.

   - Clarified that anonymous authentication involves a name value of
     zero length and a password value of zero length.  The
     unauthenticated authentication mechanism was added to handle simple
     Bind requests involving a name value with a non-zero length and a
     password value of zero length.

<span class="h3"><a class="selflink" id="appendix-B.3" href="#appendix-B.3">B.3</a>.  Changes Made to <a href="./rfc2830">RFC 2830</a></span>

   This section summarizes the substantive changes made to Sections <a href="#section-3">3</a>
   and 5 of <a href="./rfc2830">RFC 2830</a>.  Readers should consult [<a href="./rfc4511" title="&quot;Lightweight Directory Access Protocol (LDAP): The Protocol&quot;">RFC4511</a>] for summaries of
   changes to other sections.

<span class="h4"><a class="selflink" id="appendix-B.3.1" href="#appendix-B.3.1">B.3.1</a>.  <a href="#section-3.6">Section 3.6</a> ("Server Identity Check")</span>

   - Substantially updated the server identity check algorithm to ensure
     that it is complete and robust.  In particular, the use of all
     relevant values in the subjectAltName and the subjectName fields
     are covered by the algorithm and matching rules are specified for
     each type of value.  Mapped (derived) forms of the server identity
     may now be used when the mapping is performed in a secure fashion.








<span class="grey">Harrison                    Standards Track                    [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


<span class="h4"><a class="selflink" id="appendix-B.3.2" href="#appendix-B.3.2">B.3.2</a>.  <a href="#section-3.7">Section 3.7</a> ("Refresh of Server Capabilities Information")</span>

   - Clients are no longer required to always refresh information about
     server capabilities following TLS establishment.  This is to allow
     for situations where this information was obtained through a secure
     mechanism.

<span class="h4"><a class="selflink" id="appendix-B.3.3" href="#appendix-B.3.3">B.3.3</a>.  <a href="#section-5">Section 5</a> ("Effects of TLS on a Client's Authorization</span>
        Identity")

   - Establishing a TLS layer on an LDAP session may now cause the
     authorization state of the LDAP session to change.

<span class="h4"><a class="selflink" id="appendix-B.3.4" href="#appendix-B.3.4">B.3.4</a>.  <a href="#section-5.2">Section 5.2</a> ("TLS Connection Closure Effects")</span>

   - Closing a TLS layer on an LDAP session changes the authentication
     and authorization state of the LDAP session based on local policy.
     Specifically, this means that implementations are not required to
     change the authentication and authorization states to anonymous
     upon TLS closure.

   - Replaced references to <a href="./rfc2401">RFC 2401</a> with <a href="./rfc4301">RFC 4301</a>.

Author's Address

   Roger Harrison
   Novell, Inc.
   1800 S.  Novell Place
   Provo, UT 84606
   USA

   Phone: +1 801 861 2642
   EMail: roger_harrison@novell.com


















<span class="grey">Harrison                    Standards Track                    [Page 33]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
<span class="grey"><a href="./rfc4513">RFC 4513</a>              LDAP Authentication Methods              June 2006</span>


Full Copyright Statement

   Copyright (C) The Internet Society (2006).

   This document is subject to the rights, licenses and restrictions
   contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.

Acknowledgement

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).







Harrison                    Standards Track                    [Page 34]
</pre>