INTERNET-DRAFT Kurt D. Zeilenga
Intended Category: Standard Track OpenLDAP Foundation
-Expires in six months 17 May 2002
+Expires in six months 1 November 2002
LDAP "Who am I?" Operation
- <draft-zeilenga-ldap-authzid-06.txt>
+ <draft-zeilenga-ldap-authzid-08.txt>
Status of this Memo
revision, submitted to the RFC Editor as a Standard Track document.
Distribution of this memo is unlimited. Technical discussion of this
document will take place on the IETF LDAP Extension Working Group
- mailing list <ietf-ldapext@netscape.com>. Please send editorial
- comments directly to the author <Kurt@OpenLDAP.org>.
+ mailing list <ldapext@ietf.org>. Please send editorial comments
+ directly to the author <Kurt@OpenLDAP.org>.
Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other
Zeilenga LDAP "Who am I?" [Page 1]
\f
-INTERNET-DRAFT draft-zeilenga-ldap-authzid-06 17 May 2002
+INTERNET-DRAFT draft-zeilenga-ldap-authzid-08 1 November 2002
Conventions
1. Background and Intent of Use
This specification describes a Lightweight Directory Access Protocol
- (LDAP) [RFC2251] extended operation which clients can use to obtain
- the primary authorization identity in its primary form which the
- server has associated with the user or application entity.
-
- Servers often associate multiple authorization identities with the
- client and each authorization identity may be represented by multiple
- authzId [RFC2829] strings. This operation requests and returns the
- authzId the server considers to be primary. In the specification, the
- term "the authorization identity" and "the authzid" are to generally
- read as "the primary authorization identity" and the "the primary
- authzid", respectively.
+ (LDAP) [RFC3377] operation which clients can use to obtain the primary
+ authorization identity in its primary form which the server has
+ associated with the user or application entity. The operation is
+ called the "Who am I?" operation.
This specification is intended to replace the existing [AUTHCTL]
mechanism which uses Bind request and response controls to request and
return the authorization identity. Bind controls are not protected by
the security layers established by the Bind operation which they are
transferred as part of. While it is possible to establish security
- layers prior to the Bind operation, it is often desirable to only use
- security layers established by the Bind operation. An extended
- operation sent after a Bind operation is protected by the security
- layers established by the Bind operation.
+ layers using Start TLS [RFC2830] prior to the Bind operation, it is
+ often desirable to use security layers established by the Bind
+ operation. An extended operation sent after a Bind operation is
+ protected by the security layers established by the Bind operation.
There are other cases where it is desirable to request the
authorization identity which the server associated with the client
Control. The "Who am I?" operation can also be used prior to the Bind
operation.
- The LDAP "Who am I?" operation is named after the UNIX whoami(1)
- command. The whoami(1) command displays the effective user id.
+ Servers often associate multiple authorization identities with the
+ client and each authorization identity may be represented by multiple
+ authzId [RFC2829] strings. This operation requests and returns the
+ authzId the server considers to be primary. In the specification, the
+ term "the authorization identity" and "the authzId" are generally to
+ be read as "the primary authorization identity" and the "the primary
+ authzId", respectively.
2. The "Who am I?" Operation
The "Who am I?" operation is defined as an LDAP Extended Operation
+ [RFC2251, Section 4.12] identified by the whoamiOID Object Identifier
+ (OID). This section details the syntax of the operation's whoami
Zeilenga LDAP "Who am I?" [Page 2]
\f
-INTERNET-DRAFT draft-zeilenga-ldap-authzid-06 17 May 2002
+INTERNET-DRAFT draft-zeilenga-ldap-authzid-08 1 November 2002
- [RFC2251, Section 4.12] identified by the whoamiOID Object Identifier
- (OID). This section details the syntax of the operation's whoami
request and response messages.
- whoamiOID ::= "1.3.6.1.4.1.4203.1.11.3"
+ whoamiOID ::= "1.3.6.1.4.1.4203.1.11.3"
2.1. The whoami Request
example, a whoami request could be encoded as the sequence of octets
(in hex):
+ 30 1e 02 01 02 77 19 80 17 31 2e 33 2e 36 2e 31
+ 2e 34 2e 31 2e 34 32 30 33 2e 31 2e 31 31 2e 33
+
2.2. The whoami Response
The whoami response is an ExtendedResponse where the responseName
- field is absent and, if present, the response field is empty or an
+ field is absent and the response field, if present, is empty or an
authzId [RFC2829]. For example, a whoami response returning the
- authzid "u:kurt@OPENLDAP.ORG" (in response to the example request)
+ authzId "u:kurt@OPENLDAP.ORG" (in response to the example request)
would be encoded as the sequence of octets (in hex):
+ 30 21 02 01 02 78 1c 0a 01 00 04 00 04 00 8b 13
+ 75 3a 6b 75 72 74 40 4f 50 45 4e 4c 44 41 50 2e
+ 4f 52 47
3. Operational Semantics
- The function of the "Who am I?" operation is to request that the
- server returns the authorization identity it currently associates with
- the client. The client requests this authorization identity by
- issuing a whoami Request. The server responds to this request with a
- whoami Response.
+ The "Who am I?" operation provides a mechanism, a whoami Request, for
+ the client to request that the server returns the authorization
+ identity it currently associates with the client and provides a
+ mechanism, a whoami Response, for the server to respond to that
+ request.
If the server is willing and able to provide the authorization
identity it associates with the client, the server SHALL return a
whoami Response with a success resultCode. If the server is treating
- the client as an anonymous entity, the response field is empty.
- Otherwise the server is to provide the authzId [RFC2829] representing
- the authorization identity it currently associates with the client in
- the response field.
+ the client as an anonymous entity, the response field is present but
+ empty. Otherwise the server provides the authzId [RFC2829]
+ representing the authorization identity it currently associates with
+ the client in the response field.
If the server is unwilling or unable to provide the authorization
identity it associates with the client, the server SHALL return a
whoami Response with an appropriate non-success resultCode (such as
- operationsError, protocolError, confidentialityRequired,
- insufficientAccessRights, busy, unavailable, unwillingToPerform, or
- other) and an absent response field.
-
Zeilenga LDAP "Who am I?" [Page 3]
\f
-INTERNET-DRAFT draft-zeilenga-ldap-authzid-06 17 May 2002
+INTERNET-DRAFT draft-zeilenga-ldap-authzid-08 1 November 2002
+ operationsError, protocolError, confidentialityRequired,
+ insufficientAccessRights, busy, unavailable, unwillingToPerform, or
+ other) and an absent response field.
+
As described in [RFC2251] and [RFC2829], an LDAP session has an
"anonymous" association until the client has been successfully
authenticated using the Bind operation. Clients MUST NOT invoke the
4. Extending the "Who am I?" operation with controls
Future specifications may extend the "Who am I?" operation using the
- control mechanism. When extended by controls, the "Who am I?"
- operation requests and returns the authorization identity the server
- associates with the client in a particular context indicated by the
- controls.
+ control mechanism [RFC2251]. When extended by controls, the "Who am
+ I?" operation requests and returns the authorization identity the
+ server associates with the client in a particular context indicated by
+ the controls.
4.1. Proxied Authorization Control
it associates with the assumed identity.
When a Proxied Authorization Control is be attached to the "Who Am I?"
- operation, the operation requests the return of the authzid the server
+ operation, the operation requests the return of the authzId the server
associates with the identity asserted in the Proxied Authorization
Control. The TBD result code is used to indicate that the server does
not allow the client to assume the asserted identity. [[Note to RFC
Identities associated with users may be sensitive information. When
so, security layers [RFC2829][RFC2830] should be established to
- protect this information. This mechanism is specifically designed to
- allow security layers established by a Bind operation to protect the
- integrity and/or confidentiality of the authorization identity.
-
Zeilenga LDAP "Who am I?" [Page 4]
\f
-INTERNET-DRAFT draft-zeilenga-ldap-authzid-06 17 May 2002
+INTERNET-DRAFT draft-zeilenga-ldap-authzid-08 1 November 2002
+ protect this information. This mechanism is specifically designed to
+ allow security layers established by a Bind operation to protect the
+ integrity and/or confidentiality of the authorization identity.
+
Servers may place access control or other restrictions upon the use of
this operation.
- As with any other extended operations, general LDAP considerations
- apply. These are detailed in [RFC2251], [RFC2829], and [RFC2830].
+ As with any other extended operations, general LDAP security
+ considerations [RFC3377] apply.
6. IANA Considerations
- No IANA assignments are requested.
+ This OID 1.3.6.1.4.1.4203.1.11.3 to identify the LDAP "Who Am I?
+ extended operation. This OID was assigned [ASSIGN] by OpenLDAP
+ Foundation, under its IANA-assigned private enterprise allocation
+ [PRIVATE], for use in this specification.
+
+ Registration of this protocol mechansism is requested [RFC3383].
+
+ Subject: Request for LDAP Protocol Mechansism Registration
+
+ Object Identifier: 1.3.6.1.4.1.4203.1.11.3
+
+ Description: Who am I?
+
+ Person & email address to contact for further information:
+ Kurt Zeilenga <kurt@openldap.org>
+
+ Usage: Extended Operation
+
+ Specification: RFCxxxx
+
+ Author/Change Controller: IESG
- This document uses the OID 1.3.6.1.4.1.4203.1.11.3 to identify the
- LDAP "Who Am I? extended operation. This OID was assigned [ASSIGN] by
- OpenLDAP Foundation under its IANA assigned private enterprise
- allocation [PRIVATE] for use in this specification.
+ Comments: none
7. Acknowledgment
"Authentication Response Control" [AUTHCTL] by Rob Weltman, Mark Smith
and Mark Wahl.
+ The LDAP "Who am I?" operation takes it name from the UNIX whoami(1)
+ command. The whoami(1) command displays the effective user id.
+
+
+
+
+
+Zeilenga LDAP "Who am I?" [Page 5]
+\f
+INTERNET-DRAFT draft-zeilenga-ldap-authzid-08 1 November 2002
+
8. Author's Address
Access Protocol (v3): Extension for Transport Layer
Security", RFC 2830, May 2000.
+ [RFC3377] J. Hodges, R. Morgan, "Lightweight Directory Access
+ Protocol (v3): Technical Specification", RFC 3377,
+ September 2002.
+
[PROXYCTL] R. Weltman, "LDAP Proxied Authentication Control", draft-
weltman-ldapv3-proxy-xx.txt (a work in progress).
-
-Zeilenga LDAP "Who am I?" [Page 5]
-\f
-INTERNET-DRAFT draft-zeilenga-ldap-authzid-06 17 May 2002
-
-
10. Informative References
+ [RFC3383] K. Zeilenga, "IANA Considerations for LDAP", BCP 64 (also
+ RFC 3383), September 2002.
+
[ASSIGN] OpenLDAP Foundation, "OpenLDAP OID Delegations",
http://www.openldap.org/foundation/oid-delegate.txt.
Copyright 2002, The Internet Society. All Rights Reserved.
+
+
+
+Zeilenga LDAP "Who am I?" [Page 6]
+\f
+INTERNET-DRAFT draft-zeilenga-ldap-authzid-08 1 November 2002
+
+
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and
-Zeilenga LDAP "Who am I?" [Page 6]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Zeilenga LDAP "Who am I?" [Page 7]
\f
projects / openldap / blobdiff