mirror of
https://git.openldap.org/openldap/openldap.git
synced 2024-12-21 03:10:25 +08:00
284 lines
9.6 KiB
Plaintext
284 lines
9.6 KiB
Plaintext
|
||
|
||
|
||
|
||
|
||
|
||
INTERNET-DRAFT Kurt D. Zeilenga
|
||
Intended Category: Informational OpenLDAP Foundation
|
||
Expires in six months 20 December 2002
|
||
|
||
|
||
LDAP: Requesting Attributes by Object Class
|
||
<draft-zeilenga-ldap-adlist-04.txt>
|
||
|
||
|
||
Status of this Memo
|
||
|
||
This document is an Internet-Draft and is in full conformance with all
|
||
provisions of Section 10 of RFC2026.
|
||
|
||
This document is intended to be, after appropriate review and
|
||
revision, submitted to the RFC Editor as an Informational document.
|
||
Distribution of this memo is unlimited. Technical discussion of this
|
||
document will take place on the IETF LDAP Extensions Working Group
|
||
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
|
||
groups may also distribute working documents as Internet-Drafts.
|
||
Internet-Drafts are draft documents valid for a maximum of six months
|
||
and may be updated, replaced, or obsoleted by other documents at any
|
||
time. It is inappropriate to use Internet-Drafts as reference
|
||
material or to cite them other than as ``work in progress.''
|
||
|
||
The list of current Internet-Drafts can be accessed at
|
||
<http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
|
||
Internet-Draft Shadow Directories can be accessed at
|
||
<http://www.ietf.org/shadow.html>.
|
||
|
||
Copyright 2002, The Internet Society. All Rights Reserved.
|
||
|
||
Please see the Copyright section near the end of this document for
|
||
more information.
|
||
|
||
|
||
Abstract
|
||
|
||
The Lightweight Directory Access Protocol (LDAP) search operation
|
||
provides mechanisms for clients to request all user application
|
||
attributes, all operational attributes, or attributes selected by
|
||
their description. This document extends LDAP to provide a mechanism
|
||
for LDAP clients to request the return of all attributes of an object
|
||
class.
|
||
|
||
|
||
|
||
Zeilenga Requesting Attributes by Object Class [Page 1]
|
||
|
||
INTERNET-DRAFT draft-zeilenga-ldap-adlist-04 20 December 2002
|
||
|
||
|
||
1. Overview
|
||
|
||
In the Lightweight Directory Access Protocol (LDAP) [RFC3377], the
|
||
search operation [RFC2251] support requesting a sets of attributes.
|
||
This set is determined by a list of attribute descriptions. Two
|
||
special descriptors are defined to request all user attributes ("*")
|
||
[RFC2251] and all operational attributes ("+") [OPATTRS]. However,
|
||
there is no convenient mechanism for requesting pre-defined sets of
|
||
attributes.
|
||
|
||
This document extends LDAP to allow an object class identifier to be
|
||
specified in search request attributes list to request the return all
|
||
attributes allowed by object class. A plus sign ("+", U+002B) is used
|
||
to distinguish an object class identifier from an attribute
|
||
descriptions.
|
||
|
||
For example, the attribute list of "+country" is equivalent to the
|
||
attribute list of 'c', 'searchGuide', 'description', and
|
||
'objectClass'. This object class and its attributes are described in
|
||
[RFC2256].
|
||
|
||
This extension is intended to be used where the user is in direct
|
||
control of the parameters of the LDAP search operation.
|
||
|
||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
|
||
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
|
||
document are to be interpreted as described in BCP 14 [RFC2119].
|
||
|
||
|
||
2. Return of all Attributes of an Object Class
|
||
|
||
This extension allows object class identifiers is to be provided in
|
||
the attributes field of the LDAP SearchRequest [RFC2251]. For each
|
||
object class identified in the attributes field, the request is to be
|
||
treated as if each attribute allowed by that class (by "MUST" or
|
||
"MAY", directly or by SUPerior) was itself listed.
|
||
|
||
If the object class identifier is unrecognized, it is be treated an an
|
||
unrecognized attribute description.
|
||
|
||
This extension redefines the attributes field of the SearchRequest to
|
||
be a DescriptionList described by the following ASN.1 [X.680] data
|
||
type:
|
||
|
||
DescriptionList ::= SEQUENCE OF Description
|
||
Description ::= LDAPString
|
||
|
||
The Description is string conforming to the ABNF [RFC2234]:
|
||
|
||
|
||
|
||
Zeilenga Requesting Attributes by Object Class [Page 2]
|
||
|
||
INTERNET-DRAFT draft-zeilenga-ldap-adlist-04 20 December 2002
|
||
|
||
|
||
Description = AttributeDescription | ObjectClassDescription.
|
||
ObjectClassDescription = "+" ObjectClass *( ";" options )
|
||
|
||
where <AttributeDescription> and <options> productions are as defined
|
||
in Section 4.1.5 of [RFC2251] and an <ObjectClass> is an object
|
||
identifier, in either <numericoid> or <descr> form [RFC2252], of an
|
||
object class.
|
||
|
||
<ObjectClassDescription> <options> are provided for extensibility.
|
||
This document only defines semantics of <ObjectClassDescription>s with
|
||
zero options in the attributes field of a SearchRequest. Other uses
|
||
may be defined in future specifications.
|
||
|
||
Servers supporting this feature SHOULD publish the Object Identifier
|
||
1.3.6.1.4.1.4203.1.11.2 as a value of the 'supportedFeatures'
|
||
[FEATURES] attribute in the root DSE.
|
||
|
||
|
||
3. Security Considerations
|
||
|
||
This extension provides a shorthand for requesting all attributes of
|
||
an object class. As these attributes which could have been listed
|
||
individually, this short hand is not believed to raise additional
|
||
security considerations.
|
||
|
||
Implementors of this (or any) LDAP extension should be familiar with
|
||
general LDAP security considerations [RFC3377].
|
||
|
||
|
||
4. IANA Considerations
|
||
|
||
This OID 1.3.6.1.4.1.4203.1.11.2 to identify the LDAP "OC AD List?
|
||
feature. 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 per BCP 64
|
||
[RFC3383].
|
||
|
||
Subject: Request for LDAP Protocol Mechansism Registration
|
||
Object Identifier: 1.3.6.1.4.1.4203.1.5.2
|
||
Description: OC AD Lists
|
||
Person & email address to contact for further information:
|
||
Kurt Zeilenga <kurt@openldap.org>
|
||
Usage: Feature
|
||
Specification: RFCxxxx
|
||
Author/Change Controller: Kurt Zeilenga <kurt@openldap.org>
|
||
Comments: none
|
||
|
||
|
||
|
||
Zeilenga Requesting Attributes by Object Class [Page 3]
|
||
|
||
INTERNET-DRAFT draft-zeilenga-ldap-adlist-04 20 December 2002
|
||
|
||
|
||
5. Author's Address
|
||
|
||
Kurt D. Zeilenga
|
||
OpenLDAP Foundation
|
||
<Kurt@OpenLDAP.org>
|
||
|
||
|
||
6. Normative References
|
||
|
||
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
|
||
Requirement Levels", BCP 14 (also RFC 2119), March 1997.
|
||
|
||
[RFC2234] D. Crocker, P. Overell, "Augmented BNF for Syntax
|
||
Specifications: ABNF", RFC 2234, November 1997.
|
||
|
||
[RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access
|
||
Protocol (v3)", RFC 2251, December 1997.
|
||
|
||
[RFC2252] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight
|
||
Directory Access Protocol (v3): Attribute Syntax
|
||
Definitions", RFC 2252, December 1997.
|
||
|
||
[RFC3377] J. Hodges, R. Morgan, "Lightweight Directory Access
|
||
Protocol (v3): Technical Specification", RFC 3377,
|
||
September 2002.
|
||
|
||
[FEATURES] K. Zeilenga, "Feature Discovery in LDAP",
|
||
draft-zeilenga-ldap-features-xx.txt (a work in progress).
|
||
|
||
[X.680] ITU-T, "Abstract Syntax Notation One (ASN.1) -
|
||
Specification of Basic Notation", X.680, 1994.
|
||
|
||
|
||
7. Informative References
|
||
|
||
[RFC2256] M. Wahl, "A Summary of the X.500(96) User Schema for use
|
||
with LDAPv3", RFC 2256, December 1997.
|
||
|
||
[RFC3383] K. Zeilenga, "IANA Considerations for LDAP", RFC 3383,
|
||
September 2002.
|
||
|
||
[ASSIGN] OpenLDAP Foundation, "OpenLDAP OID Delegations",
|
||
http://www.openldap.org/foundation/oid-delegate.txt.
|
||
|
||
[PRIVATE] IANA, "Private Enterprise Numbers",
|
||
http://www.iana.org/assignments/enterprise-numbers.
|
||
|
||
|
||
|
||
|
||
|
||
Zeilenga Requesting Attributes by Object Class [Page 4]
|
||
|
||
INTERNET-DRAFT draft-zeilenga-ldap-adlist-04 20 December 2002
|
||
|
||
|
||
Copyright 2002, The Internet Society. All Rights Reserved.
|
||
|
||
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
|
||
distributed, in whole or in part, without restriction of any kind,
|
||
provided that the above copyright notice and this paragraph are
|
||
included on all such copies and derivative works. However, this
|
||
document itself may not be modified in any way, such as by removing
|
||
the copyright notice or references to the Internet Society or other
|
||
Internet organizations, except as needed for the purpose of
|
||
developing Internet standards in which case the procedures for
|
||
copyrights defined in the Internet Standards process must be followed,
|
||
or as required to translate it into languages other than English.
|
||
|
||
The limited permissions granted above are perpetual and will not be
|
||
revoked by the Internet Society or its successors or assigns.
|
||
|
||
This document and the information contained herein is provided on an
|
||
"AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET
|
||
ENGINEERING TASK FORCE DISCLAIMS 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.
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
Zeilenga Requesting Attributes by Object Class [Page 5]
|
||
|