source: branches/samba-3.5.x/source4/ldap_server/devdocs/rfc4519.txt

Last change on this file was 414, checked in by Herwig Bauernfeind, 15 years ago

Samba 3.5.0: Initial import
File size: 63.5 KB
Line 
1
2
3
4
5
6
7Network Working Group A. Sciberras, Ed.
8Request for Comments: 4519 eB2Bcom
9Obsoletes: 2256 June 2006
10Updates: 2247, 2798, 2377
11Category: Standards Track
12
13
14 Lightweight Directory Access Protocol (LDAP):
15 Schema for User Applications
16
17Status of This Memo
18
19 This document specifies an Internet standards track protocol for the
20 Internet community, and requests discussion and suggestions for
21 improvements. Please refer to the current edition of the "Internet
22 Official Protocol Standards" (STD 1) for the standardization state
23 and status of this protocol. Distribution of this memo is unlimited.
24
25Copyright Notice
26
27 Copyright (C) The Internet Society (2006).
28
29Abstract
30
31 This document is an integral part of the Lightweight Directory Access
32 Protocol (LDAP) technical specification. It provides a technical
33 specification of attribute types and object classes intended for use
34 by LDAP directory clients for many directory services, such as White
35 Pages. These objects are widely used as a basis for the schema in
36 many LDAP directories. This document does not cover attributes used
37 for the administration of directory servers, nor does it include
38 directory objects defined for specific uses in other documents.
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58Sciberras Standards Track [Page 1]
59
60
61RFC 4519 LDAP: Schema for User Applications June 2006
62
63
64Table of Contents
65
66 1. Introduction ....................................................3
67 1.1. Relationship with Other Specifications .....................3
68 1.2. Conventions ................................................4
69 1.3. General Issues .............................................4
70 2. Attribute Types .................................................4
71 2.1. 'businessCategory' .........................................5
72 2.2. 'c' ........................................................5
73 2.3. 'cn' .......................................................5
74 2.4. 'dc' .......................................................6
75 2.5. 'description' ..............................................6
76 2.6. 'destinationIndicator' .....................................7
77 2.7. 'distinguishedName' ........................................7
78 2.8. 'dnQualifier' ..............................................8
79 2.9. 'enhancedSearchGuide' ......................................8
80 2.10. 'facsimileTelephoneNumber' ................................9
81 2.11. 'generationQualifier' .....................................9
82 2.12. 'givenName' ...............................................9
83 2.13. 'houseIdentifier' .........................................9
84 2.14. 'initials' ...............................................10
85 2.15. 'internationalISDNNumber' ................................10
86 2.16. 'l' ......................................................10
87 2.17. 'member' .................................................11
88 2.18. 'name' ...................................................11
89 2.19. 'o' ......................................................11
90 2.20. 'ou' .....................................................12
91 2.21. 'owner' ..................................................12
92 2.22. 'physicalDeliveryOfficeName' .............................12
93 2.23. 'postalAddress' ..........................................13
94 2.24. 'postalCode' .............................................13
95 2.25. 'postOfficeBox' ..........................................14
96 2.26. 'preferredDeliveryMethod' ................................14
97 2.27. 'registeredAddress' ......................................14
98 2.28. 'roleOccupant' ...........................................15
99 2.29. 'searchGuide' ............................................15
100 2.30. 'seeAlso' ................................................15
101 2.31. 'serialNumber' ...........................................16
102 2.32. 'sn' .....................................................16
103 2.33. 'st' .....................................................16
104 2.34. 'street' .................................................17
105 2.35. 'telephoneNumber' ........................................17
106 2.36. 'teletexTerminalIdentifier' ..............................17
107 2.37. 'telexNumber' ............................................18
108 2.38. 'title' ..................................................18
109 2.39. 'uid' ....................................................18
110 2.40. 'uniqueMember' ...........................................19
111 2.41. 'userPassword' ...........................................19
112
113
114
115Sciberras Standards Track [Page 2]
116
117
118RFC 4519 LDAP: Schema for User Applications June 2006
119
120
121 2.42. 'x121Address' ............................................20
122 2.43. 'x500UniqueIdentifier' ...................................20
123 3. Object Classes .................................................20
124 3.1. 'applicationProcess' ......................................21
125 3.2. 'country' .................................................21
126 3.3. 'dcObject' ................................................21
127 3.4. 'device' ..................................................21
128 3.5. 'groupOfNames' ............................................22
129 3.6. 'groupOfUniqueNames' ......................................22
130 3.7. 'locality' ................................................23
131 3.8. 'organization' ............................................23
132 3.9. 'organizationalPerson' ....................................24
133 3.10. 'organizationalRole' .....................................24
134 3.11. 'organizationalUnit' .....................................24
135 3.12. 'person' .................................................25
136 3.13. 'residentialPerson' ......................................25
137 3.14. 'uidObject' ..............................................26
138 4. IANA Considerations ............................................26
139 5. Security Considerations ........................................28
140 6. Acknowledgements ...............................................28
141 7. References .....................................................29
142 7.1. Normative References ......................................29
143 7.2. Informative References ....................................30
144 Appendix A Changes Made Since RFC 2256 ...........................32
145
1461. Introduction
147
148 This document provides an overview of attribute types and object
149 classes intended for use by Lightweight Directory Access Protocol
150 (LDAP) directory clients for many directory services, such as White
151 Pages. Originally specified in the X.500 [X.500] documents, these
152 objects are widely used as a basis for the schema in many LDAP
153 directories. This document does not cover attributes used for the
154 administration of directory servers, nor does it include directory
155 objects defined for specific uses in other documents.
156
1571.1. Relationship with Other Specifications
158
159 This document is an integral part of the LDAP technical specification
160 [RFC4510], which obsoletes the previously defined LDAP technical
161 specification, RFC 3377, in its entirety. In terms of RFC 2256,
162 Sections 6 and 8 of RFC 2256 are obsoleted by [RFC4517]. Sections
163 5.1, 5.2, 7.1, and 7.2 of RFC 2256 are obsoleted by [RFC4512]. The
164 remainder of RFC 2256 is obsoleted by this document. The technical
165 specification for the 'dc' attribute type and 'dcObject' object class
166 found in RFC 2247 are superseded by sections 2.4 and 3.3 of this
167 document. The remainder of RFC 2247 remains in force.
168
169
170
171
172Sciberras Standards Track [Page 3]
173
174
175RFC 4519 LDAP: Schema for User Applications June 2006
176
177
178 This document updates RFC 2798 by replacing the informative
179 description of the 'uid' attribute type with the definitive
180 description provided in Section 2.39 of this document.
181
182 This document updates RFC 2377 by replacing the informative
183 description of the 'uidObject' object class with the definitive
184 description provided in Section 3.14 of this document.
185
186 A number of schema elements that were included in the previous
187 revision of the LDAP Technical Specification are not included in this
188 revision of LDAP. PKI-related schema elements are now specified in
189 [RFC4523]. Unless reintroduced in future technical specifications,
190 the remainder are to be considered Historic.
191
192 The descriptions in this document SHALL be considered definitive for
193 use in LDAP.
194
1951.2. Conventions
196
197 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
198 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
199 document are to be interpreted as described in RFC 2119 [RFC2119].
200
2011.3. General Issues
202
203 This document references Syntaxes defined in Section 3 of [RFC4517]
204 and Matching Rules defined in Section 4 of [RFC4517].
205
206 The definitions of Attribute Types and Object Classes are written
207 using the Augmented Backus-Naur Form (ABNF) [RFC4234] of
208 AttributeTypeDescription and ObjectClassDescription given in
209 [RFC4512]. Lines have been folded for readability. When such values
210 are transferred as attribute values in the LDAP Protocol, the values
211 will not contain line breaks.
212
2132. Attribute Types
214
215 The attribute types contained in this section hold user information.
216
217 There is no requirement that servers implement the 'searchGuide' and
218 'teletexTerminalIdentifier' attribute types. In fact, their use is
219 greatly discouraged.
220
221 An LDAP server implementation SHOULD recognize the rest of the
222 attribute types described in this section.
223
224
225
226
227
228
229Sciberras Standards Track [Page 4]
230
231
232RFC 4519 LDAP: Schema for User Applications June 2006
233
234
2352.1. 'businessCategory'
236
237 The 'businessCategory' attribute type describes the kinds of business
238 performed by an organization. Each kind is one value of this
239 multi-valued attribute.
240 (Source: X.520 [X.520])
241
242 ( 2.5.4.15 NAME 'businessCategory'
243 EQUALITY caseIgnoreMatch
244 SUBSTR caseIgnoreSubstringsMatch
245 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
246
247 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
248 [RFC4517].
249
250 Examples: "banking", "transportation", and "real estate".
251
2522.2. 'c'
253
254 The 'c' ('countryName' in X.500) attribute type contains a two-letter
255 ISO 3166 [ISO3166] country code.
256 (Source: X.520 [X.520])
257
258 ( 2.5.4.6 NAME 'c'
259 SUP name
260 SYNTAX 1.3.6.1.4.1.1466.115.121.1.11
261 SINGLE-VALUE )
262
263 1.3.6.1.4.1.1466.115.121.1.11 refers to the Country String syntax
264 [RFC4517].
265
266 Examples: "DE", "AU" and "FR".
267
2682.3. 'cn'
269
270 The 'cn' ('commonName' in X.500) attribute type contains names of an
271 object. Each name is one value of this multi-valued attribute. If
272 the object corresponds to a person, it is typically the person's full
273 name.
274 (Source: X.520 [X.520])
275
276 ( 2.5.4.3 NAME 'cn'
277 SUP name )
278
279 Examples: "Martin K Smith", "Marty Smith" and "printer12".
280
281
282
283
284
285
286Sciberras Standards Track [Page 5]
287
288
289RFC 4519 LDAP: Schema for User Applications June 2006
290
291
2922.4. 'dc'
293
294 The 'dc' ('domainComponent' in RFC 1274) attribute type is a string
295 holding one component, a label, of a DNS domain name
296 [RFC1034][RFC2181] naming a host [RFC1123]. That is, a value of this
297 attribute is a string of ASCII characters adhering to the following
298 ABNF [RFC4234]:
299
300 label = (ALPHA / DIGIT) [*61(ALPHA / DIGIT / HYPHEN) (ALPHA / DIGIT)]
301 ALPHA = %x41-5A / %x61-7A ; "A"-"Z" / "a"-"z"
302 DIGIT = %x30-39 ; "0"-"9"
303 HYPHEN = %x2D ; hyphen ("-")
304
305 The encoding of IA5String for use in LDAP is simply the characters of
306 the ASCII label. The equality matching rule is case insensitive, as
307 is today's DNS. (Source: RFC 2247 [RFC2247] and RFC 1274 [RFC 1274])
308
309 ( 0.9.2342.19200300.100.1.25 NAME 'dc'
310 EQUALITY caseIgnoreIA5Match
311 SUBSTR caseIgnoreIA5SubstringsMatch
312 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
313 SINGLE-VALUE )
314
315 1.3.6.1.4.1.1466.115.121.1.26 refers to the IA5 String syntax
316 [RFC4517].
317
318 Examples: Valid values include "example" and "com" but not
319 "example.com". The latter is invalid as it contains multiple domain
320 components.
321
322 It is noted that the directory service will not ensure that values of
323 this attribute conform to the host label restrictions [RFC1123]
324 illustrated by the <label> production provided above. It is the
325 directory client's responsibility to ensure that the labels it stores
326 in this attribute are appropriately restricted.
327
328 Directory applications supporting International Domain Names SHALL
329 use the ToASCII method [RFC3490] to produce the domain component
330 label. The special considerations discussed in Section 4 of RFC 3490
331 [RFC3490] should be taken, depending on whether the domain component
332 is used for "stored" or "query" purposes.
333
3342.5. 'description'
335
336 The 'description' attribute type contains human-readable descriptive
337 phrases about the object. Each description is one value of this
338 multi-valued attribute.
339 (Source: X.520 [X.520])
340
341
342
343Sciberras Standards Track [Page 6]
344
345
346RFC 4519 LDAP: Schema for User Applications June 2006
347
348
349 ( 2.5.4.13 NAME 'description'
350 EQUALITY caseIgnoreMatch
351 SUBSTR caseIgnoreSubstringsMatch
352 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
353
354 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
355 [RFC4517].
356
357 Examples: "a color printer", "Maintenance is done every Monday, at
358 1pm.", and "distribution list for all technical staff".
359
3602.6. 'destinationIndicator'
361
362 The 'destinationIndicator' attribute type contains country and city
363 strings associated with the object (the addressee) needed to provide
364 the Public Telegram Service. The strings are composed in accordance
365 with CCITT Recommendations F.1 [F.1] and F.31 [F.31]. Each string is
366 one value of this multi-valued attribute.
367 (Source: X.520 [X.520])
368
369 ( 2.5.4.27 NAME 'destinationIndicator'
370 EQUALITY caseIgnoreMatch
371 SUBSTR caseIgnoreSubstringsMatch
372 SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 )
373
374 1.3.6.1.4.1.1466.115.121.1.44 refers to the Printable String syntax
375 [RFC4517].
376
377 Examples: "AASD" as a destination indicator for Sydney, Australia.
378 "GBLD" as a destination indicator for London, United
379 Kingdom.
380
381 It is noted that the directory will not ensure that values of this
382 attribute conform to the F.1 and F.31 CCITT Recommendations. It is
383 the application's responsibility to ensure destination indicators
384 that it stores in this attribute are appropriately constructed.
385
3862.7. 'distinguishedName'
387
388 The 'distinguishedName' attribute type is not used as the name of the
389 object itself, but it is instead a base type from which some user
390 attribute types with a DN syntax can inherit.
391
392 It is unlikely that values of this type itself will occur in an
393 entry. LDAP server implementations that do not support attribute
394 subtyping need not recognize this attribute in requests. Client
395 implementations MUST NOT assume that LDAP servers are capable of
396 performing attribute subtyping.
397
398
399
400Sciberras Standards Track [Page 7]
401
402
403RFC 4519 LDAP: Schema for User Applications June 2006
404
405
406 (Source: X.520 [X.520])
407
408 ( 2.5.4.49 NAME 'distinguishedName'
409 EQUALITY distinguishedNameMatch
410 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
411
412 1.3.6.1.4.1.1466.115.121.1.12 refers to the DN syntax [RFC4517].
413
4142.8. 'dnQualifier'
415
416 The 'dnQualifier' attribute type contains disambiguating information
417 strings to add to the relative distinguished name of an entry. The
418 information is intended for use when merging data from multiple
419 sources in order to prevent conflicts between entries that would
420 otherwise have the same name. Each string is one value of this
421 multi-valued attribute. It is recommended that a value of the
422 'dnQualifier' attribute be the same for all entries from a particular
423 source.
424 (Source: X.520 [X.520])
425
426 ( 2.5.4.46 NAME 'dnQualifier'
427 EQUALITY caseIgnoreMatch
428 ORDERING caseIgnoreOrderingMatch
429 SUBSTR caseIgnoreSubstringsMatch
430 SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 )
431
432 1.3.6.1.4.1.1466.115.121.1.44 refers to the Printable String syntax
433 [RFC4517].
434
435 Examples: "20050322123345Z" - timestamps can be used to disambiguate
436 information.
437 "123456A" - serial numbers can be used to disambiguate
438 information.
439
4402.9. 'enhancedSearchGuide'
441
442 The 'enhancedSearchGuide' attribute type contains sets of information
443 for use by directory clients in constructing search filters. Each
444 set is one value of this multi-valued attribute.
445 (Source: X.520 [X.520])
446
447 ( 2.5.4.47 NAME 'enhancedSearchGuide'
448 SYNTAX 1.3.6.1.4.1.1466.115.121.1.21 )
449
450 1.3.6.1.4.1.1466.115.121.1.21 refers to the Enhanced Guide syntax
451 [RFC4517].
452
453
454
455
456
457Sciberras Standards Track [Page 8]
458
459
460RFC 4519 LDAP: Schema for User Applications June 2006
461
462
463 Examples: "person#(sn$APPROX)#wholeSubtree" and
464 "organizationalUnit#(ou$SUBSTR)#oneLevel".
465
4662.10. 'facsimileTelephoneNumber'
467
468 The 'facsimileTelephoneNumber' attribute type contains telephone
469 numbers (and, optionally, the parameters) for facsimile terminals.
470 Each telephone number is one value of this multi-valued attribute.
471 (Source: X.520 [X.520])
472
473 ( 2.5.4.23 NAME 'facsimileTelephoneNumber'
474 SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 )
475
476 1.3.6.1.4.1.1466.115.121.1.22 refers to the Facsimile Telephone
477 Number syntax [RFC4517].
478
479 Examples: "+61 3 9896 7801" and "+81 3 347 7418$fineResolution".
480
4812.11. 'generationQualifier'
482
483 The 'generationQualifier' attribute type contains name strings that
484 are typically the suffix part of a person's name. Each string is one
485 value of this multi-valued attribute.
486 (Source: X.520 [X.520])
487
488 ( 2.5.4.44 NAME 'generationQualifier'
489 SUP name )
490
491 Examples: "III", "3rd", and "Jr.".
492
4932.12. 'givenName'
494
495 The 'givenName' attribute type contains name strings that are the
496 part of a person's name that is not their surname. Each string is
497 one value of this multi-valued attribute.
498 (Source: X.520 [X.520])
499
500 ( 2.5.4.42 NAME 'givenName'
501 SUP name )
502
503 Examples: "Andrew", "Charles", and "Joanne".
504
5052.13. 'houseIdentifier'
506
507 The 'houseIdentifier' attribute type contains identifiers for a
508 building within a location. Each identifier is one value of this
509 multi-valued attribute.
510 (Source: X.520 [X.520])
511
512
513
514Sciberras Standards Track [Page 9]
515
516
517RFC 4519 LDAP: Schema for User Applications June 2006
518
519
520 ( 2.5.4.51 NAME 'houseIdentifier'
521 EQUALITY caseIgnoreMatch
522 SUBSTR caseIgnoreSubstringsMatch
523 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
524
525 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
526 [RFC4517].
527
528 Example: "20" to represent the house number 20.
529
5302.14. 'initials'
531
532 The 'initials' attribute type contains strings of initials of some or
533 all of an individual's names, except the surname(s). Each string is
534 one value of this multi-valued attribute.
535 (Source: X.520 [X.520])
536
537 ( 2.5.4.43 NAME 'initials'
538 SUP name )
539
540 Examples: "K. A." and "K".
541
5422.15. 'internationalISDNNumber'
543
544 The 'internationalISDNNumber' attribute type contains Integrated
545 Services Digital Network (ISDN) addresses, as defined in the
546 International Telecommunication Union (ITU) Recommendation E.164
547 [E.164]. Each address is one value of this multi-valued attribute.
548 (Source: X.520 [X.520])
549
550 ( 2.5.4.25 NAME 'internationalISDNNumber'
551 EQUALITY numericStringMatch
552 SUBSTR numericStringSubstringsMatch
553 SYNTAX 1.3.6.1.4.1.1466.115.121.1.36 )
554
555 1.3.6.1.4.1.1466.115.121.1.36 refers to the Numeric String syntax
556 [RFC4517].
557
558 Example: "0198 333 333".
559
5602.16. 'l'
561
562 The 'l' ('localityName' in X.500) attribute type contains names of a
563 locality or place, such as a city, county, or other geographic
564 region. Each name is one value of this multi-valued attribute.
565 (Source: X.520 [X.520])
566
567
568
569
570
571Sciberras Standards Track [Page 10]
572
573
574RFC 4519 LDAP: Schema for User Applications June 2006
575
576
577 ( 2.5.4.7 NAME 'l'
578 SUP name )
579
580 Examples: "Geneva", "Paris", and "Edinburgh".
581
5822.17. 'member'
583
584 The 'member' attribute type contains the distinguished names of
585 objects that are on a list or in a group. Each name is one value of
586 this multi-valued attribute.
587 (Source: X.520 [X.520])
588
589 ( 2.5.4.31 NAME 'member'
590 SUP distinguishedName )
591
592 Examples: "cn=James Clarke,ou=Finance,o=Widget\, Inc." and
593 "cn=John Xerri,ou=Finance,o=Widget\, Inc." may
594 be two members of the financial team (group) at Widget,
595 Inc., in which case, both of these distinguished names
596 would be present as individual values of the member
597 attribute.
598
5992.18. 'name'
600
601 The 'name' attribute type is the attribute supertype from which user
602 attribute types with the name syntax inherit. Such attribute types
603 are typically used for naming. The attribute type is multi-valued.
604
605 It is unlikely that values of this type itself will occur in an
606 entry. LDAP server implementations that do not support attribute
607 subtyping need not recognize this attribute in requests. Client
608 implementations MUST NOT assume that LDAP servers are capable of
609 performing attribute subtyping.
610 (Source: X.520 [X.520])
611
612 ( 2.5.4.41 NAME 'name'
613 EQUALITY caseIgnoreMatch
614 SUBSTR caseIgnoreSubstringsMatch
615 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
616
617 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
618 [RFC4517].
619
6202.19. 'o'
621
622 The 'o' ('organizationName' in X.500) attribute type contains the
623 names of an organization. Each name is one value of this
624 multi-valued attribute.
625
626
627
628Sciberras Standards Track [Page 11]
629
630
631RFC 4519 LDAP: Schema for User Applications June 2006
632
633
634 (Source: X.520 [X.520])
635
636 ( 2.5.4.10 NAME 'o'
637 SUP name )
638
639 Examples: "Widget", "Widget, Inc.", and "Widget, Incorporated.".
640
6412.20. 'ou'
642
643 The 'ou' ('organizationalUnitName' in X.500) attribute type contains
644 the names of an organizational unit. Each name is one value of this
645 multi-valued attribute.
646 (Source: X.520 [X.520])
647
648 ( 2.5.4.11 NAME 'ou'
649 SUP name )
650
651 Examples: "Finance", "Human Resources", and "Research and
652 Development".
653
6542.21. 'owner'
655
656 The 'owner' attribute type contains the distinguished names of
657 objects that have an ownership responsibility for the object that is
658 owned. Each owner's name is one value of this multi-valued
659 attribute.
660 (Source: X.520 [X.520])
661
662 ( 2.5.4.32 NAME 'owner'
663 SUP distinguishedName )
664
665 Example: The mailing list object, whose DN is "cn=All Employees,
666 ou=Mailing List,o=Widget\, Inc.", is owned by the Human
667 Resources Director.
668
669 Therefore, the value of the 'owner' attribute within the
670 mailing list object, would be the DN of the director (role):
671 "cn=Human Resources Director,ou=employee,o=Widget\, Inc.".
672
6732.22. 'physicalDeliveryOfficeName'
674
675 The 'physicalDeliveryOfficeName' attribute type contains names that a
676 Postal Service uses to identify a post office.
677 (Source: X.520 [X.520])
678
679
680
681
682
683
684
685Sciberras Standards Track [Page 12]
686
687
688RFC 4519 LDAP: Schema for User Applications June 2006
689
690
691 ( 2.5.4.19 NAME 'physicalDeliveryOfficeName'
692 EQUALITY caseIgnoreMatch
693 SUBSTR caseIgnoreSubstringsMatch
694 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
695
696 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
697 [RFC4517].
698
699 Examples: "Bremerhaven, Main" and "Bremerhaven, Bonnstrasse".
700
7012.23. 'postalAddress'
702
703 The 'postalAddress' attribute type contains addresses used by a
704 Postal Service to perform services for the object. Each address is
705 one value of this multi-valued attribute.
706 (Source: X.520 [X.520])
707
708 ( 2.5.4.16 NAME 'postalAddress'
709 EQUALITY caseIgnoreListMatch
710 SUBSTR caseIgnoreListSubstringsMatch
711 SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
712
713 1.3.6.1.4.1.1466.115.121.1.41 refers to the Postal Address syntax
714 [RFC4517].
715
716 Example: "15 Main St.$Ottawa$Canada".
717
7182.24. 'postalCode'
719
720 The 'postalCode' attribute type contains codes used by a Postal
721 Service to identify postal service zones. Each code is one value of
722 this multi-valued attribute.
723 (Source: X.520 [X.520])
724
725 ( 2.5.4.17 NAME 'postalCode'
726 EQUALITY caseIgnoreMatch
727 SUBSTR caseIgnoreSubstringsMatch
728 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
729
730 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
731 [RFC4517].
732
733 Example: "22180", to identify Vienna, VA, in the USA.
734
735
736
737
738
739
740
741
742Sciberras Standards Track [Page 13]
743
744
745RFC 4519 LDAP: Schema for User Applications June 2006
746
747
7482.25. 'postOfficeBox'
749
750 The 'postOfficeBox' attribute type contains postal box identifiers
751 that a Postal Service uses when a customer arranges to receive mail
752 at a box on the premises of the Postal Service. Each postal box
753 identifier is a single value of this multi-valued attribute.
754 (Source: X.520 [X.520])
755
756 ( 2.5.4.18 NAME 'postOfficeBox'
757 EQUALITY caseIgnoreMatch
758 SUBSTR caseIgnoreSubstringsMatch
759 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
760
761 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
762 [RFC4517].
763
764 Example: "Box 45".
765
7662.26. 'preferredDeliveryMethod'
767
768 The 'preferredDeliveryMethod' attribute type contains an indication
769 of the preferred method of getting a message to the object.
770 (Source: X.520 [X.520])
771
772 ( 2.5.4.28 NAME 'preferredDeliveryMethod'
773 SYNTAX 1.3.6.1.4.1.1466.115.121.1.14
774 SINGLE-VALUE )
775
776 1.3.6.1.4.1.1466.115.121.1.14 refers to the Delivery Method syntax
777 [RFC4517].
778
779 Example: If the mhs-delivery Delivery Method is preferred over
780 telephone-delivery, which is preferred over all other
781 methods, the value would be: "mhs $ telephone".
782
7832.27. 'registeredAddress'
784
785 The 'registeredAddress' attribute type contains postal addresses
786 suitable for reception of telegrams or expedited documents, where it
787 is necessary to have the recipient accept delivery. Each address is
788 one value of this multi-valued attribute.
789 (Source: X.520 [X.520])
790
791 ( 2.5.4.26 NAME 'registeredAddress'
792 SUP postalAddress
793 SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
794
795
796
797
798
799Sciberras Standards Track [Page 14]
800
801
802RFC 4519 LDAP: Schema for User Applications June 2006
803
804
805 1.3.6.1.4.1.1466.115.121.1.41 refers to the Postal Address syntax
806 [RFC4517].
807
808 Example: "Receptionist$Widget, Inc.$15 Main St.$Ottawa$Canada".
809
8102.28. 'roleOccupant'
811
812 The 'roleOccupant' attribute type contains the distinguished names of
813 objects (normally people) that fulfill the responsibilities of a role
814 object. Each distinguished name is one value of this multi-valued
815 attribute.
816 (Source: X.520 [X.520])
817
818 ( 2.5.4.33 NAME 'roleOccupant'
819 SUP distinguishedName )
820
821 Example: The role object, "cn=Human Resources
822 Director,ou=Position,o=Widget\, Inc.", is fulfilled by two
823 people whose object names are "cn=Mary
824 Smith,ou=employee,o=Widget\, Inc." and "cn=James
825 Brown,ou=employee,o=Widget\, Inc.". The 'roleOccupant'
826 attribute will contain both of these distinguished names,
827 since they are the occupants of this role.
828
8292.29. 'searchGuide'
830
831 The 'searchGuide' attribute type contains sets of information for use
832 by clients in constructing search filters. It is superseded by
833 'enhancedSearchGuide', described above in Section 2.9. Each set is
834 one value of this multi-valued attribute.
835 (Source: X.520 [X.520])
836
837 ( 2.5.4.14 NAME 'searchGuide'
838 SYNTAX 1.3.6.1.4.1.1466.115.121.1.25 )
839
840 1.3.6.1.4.1.1466.115.121.1.25 refers to the Guide syntax [RFC4517].
841
842 Example: "person#sn$EQ".
843
8442.30. 'seeAlso'
845
846 The 'seeAlso' attribute type contains the distinguished names of
847 objects that are related to the subject object. Each related object
848 name is one value of this multi-valued attribute.
849 (Source: X.520 [X.520])
850
851 ( 2.5.4.34 NAME 'seeAlso'
852 SUP distinguishedName )
853
854
855
856Sciberras Standards Track [Page 15]
857
858
859RFC 4519 LDAP: Schema for User Applications June 2006
860
861
862 Example: The person object "cn=James Brown,ou=employee,o=Widget\,
863 Inc." is related to the role objects "cn=Football Team
864 Captain,ou=sponsored activities,o=Widget\, Inc." and
865 "cn=Chess Team,ou=sponsored activities,o=Widget\, Inc.".
866 Since the role objects are related to the person object, the
867 'seeAlso' attribute will contain the distinguished name of
868 each role object as separate values.
869
8702.31. 'serialNumber'
871
872 The 'serialNumber' attribute type contains the serial numbers of
873 devices. Each serial number is one value of this multi-valued
874 attribute.
875 (Source: X.520 [X.520])
876
877 ( 2.5.4.5 NAME 'serialNumber'
878 EQUALITY caseIgnoreMatch
879 SUBSTR caseIgnoreSubstringsMatch
880 SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 )
881
882 1.3.6.1.4.1.1466.115.121.1.44 refers to the Printable String syntax
883 [RFC4517].
884
885 Examples: "WI-3005" and "XF551426".
886
8872.32. 'sn'
888
889 The 'sn' ('surname' in X.500) attribute type contains name strings
890 for the family names of a person. Each string is one value of this
891 multi-valued attribute.
892 (Source: X.520 [X.520])
893
894 ( 2.5.4.4 NAME 'sn'
895 SUP name )
896
897 Example: "Smith".
898
8992.33. 'st'
900
901 The 'st' ('stateOrProvinceName' in X.500) attribute type contains the
902 full names of states or provinces. Each name is one value of this
903 multi-valued attribute.
904 (Source: X.520 [X.520])
905
906 ( 2.5.4.8 NAME 'st'
907 SUP name )
908
909 Example: "California".
910
911
912
913Sciberras Standards Track [Page 16]
914
915
916RFC 4519 LDAP: Schema for User Applications June 2006
917
918
9192.34. 'street'
920
921 The 'street' ('streetAddress' in X.500) attribute type contains site
922 information from a postal address (i.e., the street name, place,
923 avenue, and the house number). Each street is one value of this
924 multi-valued attribute.
925 (Source: X.520 [X.520])
926
927 ( 2.5.4.9 NAME 'street'
928 EQUALITY caseIgnoreMatch
929 SUBSTR caseIgnoreSubstringsMatch
930 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
931
932 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
933 [RFC4517].
934
935 Example: "15 Main St.".
936
9372.35. 'telephoneNumber'
938
939 The 'telephoneNumber' attribute type contains telephone numbers that
940 comply with the ITU Recommendation E.123 [E.123]. Each number is one
941 value of this multi-valued attribute.
942 (Source: X.520 [X.520])
943
944 ( 2.5.4.20 NAME 'telephoneNumber'
945 EQUALITY telephoneNumberMatch
946 SUBSTR telephoneNumberSubstringsMatch
947 SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
948
949 1.3.6.1.4.1.1466.115.121.1.50 refers to the Telephone Number syntax
950 [RFC4517].
951
952 Example: "+1 234 567 8901".
953
9542.36. 'teletexTerminalIdentifier'
955
956 The withdrawal of Recommendation F.200 has resulted in the withdrawal
957 of this attribute.
958 (Source: X.520 [X.520])
959
960 ( 2.5.4.22 NAME 'teletexTerminalIdentifier'
961 SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 )
962
963 1.3.6.1.4.1.1466.115.121.1.51 refers to the Teletex Terminal
964 Identifier syntax [RFC4517].
965
966
967
968
969
970Sciberras Standards Track [Page 17]
971
972
973RFC 4519 LDAP: Schema for User Applications June 2006
974
975
9762.37. 'telexNumber'
977
978 The 'telexNumber' attribute type contains sets of strings that are a
979 telex number, country code, and answerback code of a telex terminal.
980 Each set is one value of this multi-valued attribute.
981 (Source: X.520 [X.520])
982
983 ( 2.5.4.21 NAME 'telexNumber'
984 SYNTAX 1.3.6.1.4.1.1466.115.121.1.52 )
985
986 1.3.6.1.4.1.1466.115.121.1.52 refers to the Telex Number syntax
987 [RFC4517].
988
989 Example: "12345$023$ABCDE".
990
9912.38. 'title'
992
993 The 'title' attribute type contains the title of a person in their
994 organizational context. Each title is one value of this multi-valued
995 attribute.
996 (Source: X.520 [X.520])
997
998 ( 2.5.4.12 NAME 'title'
999 SUP name )
1000 Examples: "Vice President", "Software Engineer", and "CEO".
1001
10022.39. 'uid'
1003
1004 The 'uid' ('userid' in RFC 1274) attribute type contains computer
1005 system login names associated with the object. Each name is one
1006 value of this multi-valued attribute.
1007 (Source: RFC 2798 [RFC2798] and RFC 1274 [RFC1274])
1008
1009 ( 0.9.2342.19200300.100.1.1 NAME 'uid'
1010 EQUALITY caseIgnoreMatch
1011 SUBSTR caseIgnoreSubstringsMatch
1012 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
1013
1014 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
1015 [RFC4517].
1016
1017 Examples: "s9709015", "admin", and "Administrator".
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027Sciberras Standards Track [Page 18]
1028
1029
1030RFC 4519 LDAP: Schema for User Applications June 2006
1031
1032
10332.40. 'uniqueMember'
1034
1035 The 'uniqueMember' attribute type contains the distinguished names of
1036 an object that is on a list or in a group, where the relative
1037 distinguished names of the object include a value that distinguishes
1038 between objects when a distinguished name has been reused. Each
1039 distinguished name is one value of this multi-valued attribute.
1040 (Source: X.520 [X.520])
1041
1042 ( 2.5.4.50 NAME 'uniqueMember'
1043 EQUALITY uniqueMemberMatch
1044 SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 )
1045
1046 1.3.6.1.4.1.1466.115.121.1.34 refers to the Name and Optional UID
1047 syntax [RFC4517].
1048
1049 Example: If "ou=1st Battalion,o=Defense,c=US" is a battalion that was
1050 disbanded, establishing a new battalion with the "same" name
1051 would have a unique identifier value added, resulting in
1052 "ou=1st Battalion, o=Defense,c=US#'010101'B".
1053
10542.41. 'userPassword'
1055
1056 The 'userPassword' attribute contains octet strings that are known
1057 only to the user and the system to which the user has access. Each
1058 string is one value of this multi-valued attribute.
1059
1060 The application SHOULD prepare textual strings used as passwords by
1061 transcoding them to Unicode, applying SASLprep [RFC4013], and
1062 encoding as UTF-8. The determination of whether a password is
1063 textual is a local client matter.
1064 (Source: X.509 [X.509])
1065
1066 ( 2.5.4.35 NAME 'userPassword'
1067 EQUALITY octetStringMatch
1068 SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 )
1069
1070 1.3.6.1.4.1.1466.115.121.1.40 refers to the Octet String syntax
1071 [RFC4517].
1072
1073 Passwords are stored using an Octet String syntax and are not
1074 encrypted. Transfer of cleartext passwords is strongly discouraged
1075 where the underlying transport service cannot guarantee
1076 confidentiality and may result in disclosure of the password to
1077 unauthorized parties.
1078
1079 An example of a need for multiple values in the 'userPassword'
1080 attribute is an environment where every month the user is expected to
1081
1082
1083
1084Sciberras Standards Track [Page 19]
1085
1086
1087RFC 4519 LDAP: Schema for User Applications June 2006
1088
1089
1090 use a different password generated by some automated system. During
1091 transitional periods, like the last and first day of the periods, it
1092 may be necessary to allow two passwords for the two consecutive
1093 periods to be valid in the system.
1094
10952.42. 'x121Address'
1096
1097 The 'x121Address' attribute type contains data network addresses as
1098 defined by ITU Recommendation X.121 [X.121]. Each address is one
1099 value of this multi-valued attribute.
1100 (Source: X.520 [X.520])
1101
1102 ( 2.5.4.24 NAME 'x121Address'
1103 EQUALITY numericStringMatch
1104 SUBSTR numericStringSubstringsMatch
1105 SYNTAX 1.3.6.1.4.1.1466.115.121.1.36 )
1106
1107 1.3.6.1.4.1.1466.115.121.1.36 refers to the Numeric String syntax
1108 [RFC4517].
1109
1110 Example: "36111222333444555".
1111
11122.43. 'x500UniqueIdentifier'
1113
1114 The 'x500UniqueIdentifier' attribute type contains binary strings
1115 that are used to distinguish between objects when a distinguished
1116 name has been reused. Each string is one value of this multi-valued
1117 attribute.
1118
1119 In X.520 [X.520], this attribute type is called 'uniqueIdentifier'.
1120 This is a different attribute type from both the 'uid' and
1121 'uniqueIdentifier' LDAP attribute types. The 'uniqueIdentifier'
1122 attribute type is defined in [RFC4524].
1123 (Source: X.520 [X.520])
1124
1125 ( 2.5.4.45 NAME 'x500UniqueIdentifier'
1126 EQUALITY bitStringMatch
1127 SYNTAX 1.3.6.1.4.1.1466.115.121.1.6 )
1128
1129 1.3.6.1.4.1.1466.115.121.1.6 refers to the Bit String syntax
1130 [RFC4517].
1131
11323. Object Classes
1133
1134 LDAP servers SHOULD recognize all the Object Classes listed here as
1135 values of the 'objectClass' attribute (see [RFC4512]).
1136
1137
1138
1139
1140
1141Sciberras Standards Track [Page 20]
1142
1143
1144RFC 4519 LDAP: Schema for User Applications June 2006
1145
1146
11473.1. 'applicationProcess'
1148
1149 The 'applicationProcess' object class definition is the basis of an
1150 entry that represents an application executing in a computer system.
1151 (Source: X.521 [X.521])
1152
1153 ( 2.5.6.11 NAME 'applicationProcess'
1154 SUP top
1155 STRUCTURAL
1156 MUST cn
1157 MAY ( seeAlso $
1158 ou $
1159 l $
1160 description ) )
1161
11623.2. 'country'
1163
1164 The 'country' object class definition is the basis of an entry that
1165 represents a country.
1166 (Source: X.521 [X.521])
1167
1168 ( 2.5.6.2 NAME 'country'
1169 SUP top
1170 STRUCTURAL
1171 MUST c
1172 MAY ( searchGuide $
1173 description ) )
1174
11753.3. 'dcObject'
1176
1177 The 'dcObject' object class permits an entry to contains domain
1178 component information. This object class is defined as auxiliary,
1179 because it will be used in conjunction with an existing structural
1180 object class.
1181 (Source: RFC 2247 [RFC2247])
1182
1183 ( 1.3.6.1.4.1.1466.344 NAME 'dcObject'
1184 SUP top
1185 AUXILIARY
1186 MUST dc )
1187
11883.4. 'device'
1189
1190 The 'device' object class is the basis of an entry that represents an
1191 appliance, computer, or network element.
1192 (Source: X.521 [X.521])
1193
1194
1195
1196
1197
1198Sciberras Standards Track [Page 21]
1199
1200
1201RFC 4519 LDAP: Schema for User Applications June 2006
1202
1203
1204 ( 2.5.6.14 NAME 'device'
1205 SUP top
1206 STRUCTURAL
1207 MUST cn
1208 MAY ( serialNumber $
1209 seeAlso $
1210 owner $
1211 ou $
1212 o $
1213 l $
1214 description ) )
1215
12163.5. 'groupOfNames'
1217
1218 The 'groupOfNames' object class is the basis of an entry that
1219 represents a set of named objects including information related to
1220 the purpose or maintenance of the set.
1221 (Source: X.521 [X.521])
1222
1223 ( 2.5.6.9 NAME 'groupOfNames'
1224 SUP top
1225 STRUCTURAL
1226 MUST ( member $
1227 cn )
1228 MAY ( businessCategory $
1229 seeAlso $
1230 owner $
1231 ou $
1232 o $
1233 description ) )
1234
12353.6. 'groupOfUniqueNames'
1236
1237 The 'groupOfUniqueNames' object class is the same as the
1238 'groupOfNames' object class except that the object names are not
1239 repeated or reassigned within a set scope.
1240 (Source: X.521 [X.521])
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255Sciberras Standards Track [Page 22]
1256
1257
1258RFC 4519 LDAP: Schema for User Applications June 2006
1259
1260
1261 ( 2.5.6.17 NAME 'groupOfUniqueNames'
1262 SUP top
1263 STRUCTURAL
1264 MUST ( uniqueMember $
1265 cn )
1266 MAY ( businessCategory $
1267 seeAlso $
1268 owner $
1269 ou $
1270 o $
1271 description ) )
1272
12733.7. 'locality'
1274
1275 The 'locality' object class is the basis of an entry that represents
1276 a place in the physical world.
1277 (Source: X.521 [X.521])
1278
1279 ( 2.5.6.3 NAME 'locality'
1280 SUP top
1281 STRUCTURAL
1282 MAY ( street $
1283 seeAlso $
1284 searchGuide $
1285 st $
1286 l $
1287 description ) )
1288
12893.8. 'organization'
1290
1291 The 'organization' object class is the basis of an entry that
1292 represents a structured group of people.
1293 (Source: X.521 [X.521])
1294
1295 ( 2.5.6.4 NAME 'organization'
1296 SUP top
1297 STRUCTURAL
1298 MUST o
1299 MAY ( userPassword $ searchGuide $ seeAlso $
1300 businessCategory $ x121Address $ registeredAddress $
1301 destinationIndicator $ preferredDeliveryMethod $
1302 telexNumber $ teletexTerminalIdentifier $
1303 telephoneNumber $ internationalISDNNumber $
1304 facsimileTelephoneNumber $ street $ postOfficeBox $
1305 postalCode $ postalAddress $ physicalDeliveryOfficeName $
1306 st $ l $ description ) )
1307
1308
1309
1310
1311
1312Sciberras Standards Track [Page 23]
1313
1314
1315RFC 4519 LDAP: Schema for User Applications June 2006
1316
1317
13183.9. 'organizationalPerson'
1319
1320 The 'organizationalPerson' object class is the basis of an entry that
1321 represents a person in relation to an organization.
1322 (Source: X.521 [X.521])
1323
1324 ( 2.5.6.7 NAME 'organizationalPerson'
1325 SUP person
1326 STRUCTURAL
1327 MAY ( title $ x121Address $ registeredAddress $
1328 destinationIndicator $ preferredDeliveryMethod $
1329 telexNumber $ teletexTerminalIdentifier $
1330 telephoneNumber $ internationalISDNNumber $
1331 facsimileTelephoneNumber $ street $ postOfficeBox $
1332 postalCode $ postalAddress $ physicalDeliveryOfficeName $
1333 ou $ st $ l ) )
1334
13353.10. 'organizationalRole'
1336
1337 The 'organizationalRole' object class is the basis of an entry that
1338 represents a job, function, or position in an organization.
1339 (Source: X.521 [X.521])
1340
1341 ( 2.5.6.8 NAME 'organizationalRole'
1342 SUP top
1343 STRUCTURAL
1344 MUST cn
1345 MAY ( x121Address $ registeredAddress $ destinationIndicator $
1346 preferredDeliveryMethod $ telexNumber $
1347 teletexTerminalIdentifier $ telephoneNumber $
1348 internationalISDNNumber $ facsimileTelephoneNumber $
1349 seeAlso $ roleOccupant $ preferredDeliveryMethod $
1350 street $ postOfficeBox $ postalCode $ postalAddress $
1351 physicalDeliveryOfficeName $ ou $ st $ l $
1352 description ) )
1353
13543.11. 'organizationalUnit'
1355
1356 The 'organizationalUnit' object class is the basis of an entry that
1357 represents a piece of an organization.
1358 (Source: X.521 [X.521])
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369Sciberras Standards Track [Page 24]
1370
1371
1372RFC 4519 LDAP: Schema for User Applications June 2006
1373
1374
1375 ( 2.5.6.5 NAME 'organizationalUnit'
1376 SUP top
1377 STRUCTURAL
1378 MUST ou
1379 MAY ( businessCategory $ description $ destinationIndicator $
1380 facsimileTelephoneNumber $ internationalISDNNumber $ l $
1381 physicalDeliveryOfficeName $ postalAddress $ postalCode $
1382 postOfficeBox $ preferredDeliveryMethod $
1383 registeredAddress $ searchGuide $ seeAlso $ st $ street $
1384 telephoneNumber $ teletexTerminalIdentifier $
1385 telexNumber $ userPassword $ x121Address ) )
1386
13873.12 'person'
1388
1389 The 'person' object class is the basis of an entry that represents a
1390 human being.
1391 (Source: X.521 [X.521])
1392
1393 ( 2.5.6.6 NAME 'person'
1394 SUP top
1395 STRUCTURAL
1396 MUST ( sn $
1397 cn )
1398 MAY ( userPassword $
1399 telephoneNumber $
1400 seeAlso $ description ) )
1401
14023.13. 'residentialPerson'
1403
1404 The 'residentialPerson' object class is the basis of an entry that
1405 includes a person's residence in the representation of the person.
1406 (Source: X.521 [X.521])
1407
1408 ( 2.5.6.10 NAME 'residentialPerson'
1409 SUP person
1410 STRUCTURAL
1411 MUST l
1412 MAY ( businessCategory $ x121Address $ registeredAddress $
1413 destinationIndicator $ preferredDeliveryMethod $
1414 telexNumber $ teletexTerminalIdentifier $
1415 telephoneNumber $ internationalISDNNumber $
1416 facsimileTelephoneNumber $ preferredDeliveryMethod $
1417 street $ postOfficeBox $ postalCode $ postalAddress $
1418 physicalDeliveryOfficeName $ st $ l ) )
1419
1420
1421
1422
1423
1424
1425
1426Sciberras Standards Track [Page 25]
1427
1428
1429RFC 4519 LDAP: Schema for User Applications June 2006
1430
1431
14323.14. 'uidObject'
1433
1434 The 'uidObject' object class permits an entry to contains user
1435 identification information. This object class is defined as
1436 auxiliary, because it will be used in conjunction with an existing
1437 structural object class.
1438 (Source: RFC 2377 [RFC2377])
1439
1440 ( 1.3.6.1.1.3.1 NAME 'uidObject'
1441 SUP top
1442 AUXILIARY
1443 MUST uid )
1444
14454. IANA Considerations
1446
1447 The Internet Assigned Numbers Authority (IANA) has updated the LDAP
1448 descriptors registry as indicated in the following template:
1449
1450 Subject: Request for LDAP Descriptor Registration Update
1451 Descriptor (short name): see comments
1452 Object Identifier: see comments
1453 Person & email address to contact for further information:
1454 Andrew Sciberras <andrew.sciberras@eb2bcom.com>
1455 Usage: (A = attribute type, O = Object Class) see comment
1456 Specification: RFC 4519
1457 Author/Change Controller: IESG
1458
1459 Comments
1460
1461 In the LDAP descriptors registry, the following descriptors (short
1462 names) have been updated to refer to RFC 4519. Names that need to
1463 be reserved, rather than assigned to an Object Identifier, will
1464 contain an Object Identifier value of RESERVED.
1465
1466 NAME Type OID
1467 ------------------------ ---- ----------------------------
1468 applicationProcess O 2.5.6.11
1469 businessCategory A 2.5.4.15
1470 c A 2.5.4.6
1471 cn A 2.5.4.3
1472 commonName A 2.5.4.3
1473 country O 2.5.6.2
1474 countryName A 2.5.4.6
1475 dc A 0.9.2342.19200300.100.1.25
1476 dcObject O 1.3.6.1.4.1.1466.344
1477 description A 2.5.4.13
1478 destinationIndicator A 2.5.4.27
1479 device O 2.5.6.14
1480
1481
1482
1483Sciberras Standards Track [Page 26]
1484
1485
1486RFC 4519 LDAP: Schema for User Applications June 2006
1487
1488
1489 NAME Type OID
1490 ------------------------ ---- ----------------------------
1491 distinguishedName A 2.5.4.49
1492 dnQualifier A 2.5.4.46
1493 domainComponent A 0.9.2342.19200300.100.1.25
1494 enhancedSearchGuide A 2.5.4.47
1495 facsimileTelephoneNumber A 2.5.4.23
1496 generationQualifier A 2.5.4.44
1497 givenName A 2.5.4.42
1498 gn A RESERVED
1499 groupOfNames O 2.5.6.9
1500 groupOfUniqueNames O 2.5.6.17
1501 houseIdentifier A 2.5.4.51
1502 initials A 2.5.4.43
1503 internationalISDNNumber A 2.5.4.25
1504 l A 2.5.4.7
1505 locality O 2.5.6.3
1506 localityName A 2.5.4.7
1507 member A 2.5.4.31
1508 name A 2.5.4.41
1509 o A 2.5.4.10
1510 organization O 2.5.6.4
1511 organizationName A 2.5.4.10
1512 organizationalPerson O 2.5.6.7
1513 organizationalRole O 2.5.6.8
1514 organizationalUnit O 2.5.6.5
1515 organizationalUnitName A 2.5.4.11
1516 ou A 2.5.4.11
1517 owner A 2.5.4.32
1518 person O 2.5.6.6
1519 physicalDeliveryOfficeName A 2.5.4.19
1520 postalAddress A 2.5.4.16
1521 postalCode A 2.5.4.17
1522 postOfficeBox A 2.5.4.18
1523 preferredDeliveryMethod A 2.5.4.28
1524 registeredAddress A 2.5.4.26
1525 residentialPerson O 2.5.6.10
1526 roleOccupant A 2.5.4.33
1527 searchGuide A 2.5.4.14
1528 seeAlso A 2.5.4.34
1529 serialNumber A 2.5.4.5
1530 sn A 2.5.4.4
1531 st A 2.5.4.8
1532 street A 2.5.4.9
1533 surname A 2.5.4.4
1534 telephoneNumber A 2.5.4.20
1535 teletexTerminalIdentifier A 2.5.4.22
1536 telexNumber A 2.5.4.21
1537
1538
1539
1540Sciberras Standards Track [Page 27]
1541
1542
1543RFC 4519 LDAP: Schema for User Applications June 2006
1544
1545
1546 NAME Type OID
1547 ------------------------ ---- ----------------------------
1548 title A 2.5.4.12
1549 uid A 0.9.2342.19200300.100.1.1
1550 uidObject O 1.3.6.1.1.3.1
1551 uniqueMember A 2.5.4.50
1552 userid A 0.9.2342.19200300.100.1.1
1553 userPassword A 2.5.4.35
1554 x121Address A 2.5.4.24
1555 x500UniqueIdentifier A 2.5.4.45
1556
15575. Security Considerations
1558
1559 Attributes of directory entries are used to provide descriptive
1560 information about the real-world objects they represent, which can be
1561 people, organizations, or devices. Most countries have privacy laws
1562 regarding the publication of information about people.
1563
1564 Transfer of cleartext passwords is strongly discouraged where the
1565 underlying transport service cannot guarantee confidentiality and
1566 integrity, since this may result in disclosure of the password to
1567 unauthorized parties.
1568
1569 Multiple attribute values for the 'userPassword' attribute need to be
1570 used with care. Especially reset/deletion of a password by an
1571 administrator without knowing the old user password gets tricky or
1572 impossible if multiple values for different applications are present.
1573
1574 Certainly, applications that intend to replace the 'userPassword'
1575 value(s) with new value(s) should use modify/replaceValues (or
1576 modify/deleteAttribute+addAttribute). In addition, server
1577 implementations are encouraged to provide administrative controls
1578 that, if enabled, restrict the 'userPassword' attribute to one value.
1579
1580 Note that when used for authentication purposes [RFC4513], the user
1581 need only prove knowledge of one of the values, not all of the
1582 values.
1583
15846. Acknowledgements
1585
1586 The definitions, on which this document is based, have been developed
1587 by committees for telecommunications and international standards.
1588
1589 This document is an update of RFC 2256 by Mark Wahl. RFC 2256 was a
1590 product of the IETF ASID Working Group.
1591
1592
1593
1594
1595
1596
1597Sciberras Standards Track [Page 28]
1598
1599
1600RFC 4519 LDAP: Schema for User Applications June 2006
1601
1602
1603 The 'dc' attribute type definition and the 'dcObject' object class
1604 definition in this document supersede the specification in RFC 2247
1605 by S. Kille, M. Wahl, A. Grimstad, R. Huber, and S. Sataluri.
1606
1607 The 'uid' attribute type definition in this document supersedes the
1608 specification of the 'userid' in RFC 1274 by P. Barker and S. Kille
1609 and of the uid in RFC 2798 by M. Smith.
1610
1611 The 'uidObject' object class definition in this document supersedes
1612 the specification of the 'uidObject' in RFC 2377 by A. Grimstad, R.
1613 Huber, S. Sataluri, and M. Wahl.
1614
1615 This document is based upon input of the IETF LDAPBIS working group.
1616 The author wishes to thank S. Legg and K. Zeilenga for their
1617 significant contribution to this update. The author would also like
1618 to thank Kathy Dally, who edited early versions of this document.
1619
16207. References
1621
16227.1. Normative References
1623
1624 [E.123] Notation for national and international telephone numbers,
1625 ITU-T Recommendation E.123, 1988
1626
1627 [E.164] The international public telecommunication numbering plan,
1628 ITU-T Recommendation E.164, 1997
1629
1630 [F.1] Operational Provisions For The International Public
1631 Telegram Service Transmission System, CCITT Recommendation
1632 F.1, 1992
1633
1634 [F.31] Telegram Retransmission System, CCITT Recommendation F.31,
1635 1988
1636
1637 [ISO3166] ISO 3166, "Codes for the representation of names of
1638 countries".
1639
1640 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
1641 STD 13, RFC 1034, November 1987.
1642
1643 [RFC1123] Braden, R., "Requirements for Internet Hosts - Application
1644 and Support", STD 3, RFC 1123, October 1989.
1645
1646 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
1647 Requirement Levels", BCP 14, RFC 2119, March 1997.
1648
1649 [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
1650 Specification", RFC 2181, July 1997.
1651
1652
1653
1654Sciberras Standards Track [Page 29]
1655
1656
1657RFC 4519 LDAP: Schema for User Applications June 2006
1658
1659
1660 [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello,
1661 "Internationalizing Domain Names in Applications (IDNA)",
1662 RFC 3490, March 2003.
1663
1664 [RFC4013] Zeilenga, K., "SASLprep: Stringprep Profile for User Names
1665 and Passwords", RFC 4013, February 2005.
1666
1667 [RFC4234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
1668 Specifications: ABNF", RFC 4234, October 2005.
1669
1670 [RFC4510] Zeilenga, K., Ed., "Lightweight Directory Access Protocol
1671 (LDAP): Technical Specification Road Map", RFC 4510, June
1672 2006.
1673
1674 [RFC4512] Zeilenga, K., "Lightweight Directory Access Protocol
1675 (LDAP): Directory Information Models", RFC 4512, June
1676 2006.
1677
1678 [RFC4517] Legg, S., Ed., "Lightweight Directory Access Protocol
1679 (LDAP): Syntaxes and Matching Rules", RFC 4517, June 2006.
1680
1681 [X.121] International numbering plan for public data networks,
1682 ITU-T Recommendation X.121, 1996
1683
1684 [X.509] The Directory: Authentication Framework, ITU-T
1685 Recommendation X.509, 1993
1686
1687 [X.520] The Directory: Selected Attribute Types, ITU-T
1688 Recommendation X.520, 1993
1689
1690 [X.521] The Directory: Selected Object Classes. ITU-T
1691 Recommendation X.521, 1993
1692
16937.2. Informative References
1694
1695 [RFC1274] Barker, P. and S. Kille, "The COSINE and Internet X.500
1696 Schema", RFC 1274, November 1991.
1697
1698 [RFC2247] Kille, S., Wahl, M., Grimstad, A., Huber, R., and S.
1699 Sataluri, "Using Domains in LDAP/X.500 Distinguished
1700 Names", RFC 2247, January 1998.
1701
1702 [RFC2377] Grimstad, A., Huber, R., Sataluri, S., and M. Wahl,
1703 "Naming Plan for Internet Directory-Enabled Applications",
1704 RFC 2377, September 1998.
1705
1706 [RFC2798] Smith, M., "Definition of the inetOrgPerson LDAP Object
1707 Class", RFC 2798, April 2000.
1708
1709
1710
1711Sciberras Standards Track [Page 30]
1712
1713
1714RFC 4519 LDAP: Schema for User Applications June 2006
1715
1716
1717 [RFC4513] Harrison R., Ed., "Lightweight Directory Access Protocol
1718 (LDAP): Authentication Methods and Security Mechanisms",
1719 RFC 4513, June 2006.
1720
1721 [RFC4523] Zeilenga, K., "Lightweight Directory Access Protocol
1722 (LDAP) Schema Definitions for X.509 Certificates", RFC
1723 4523, June 2006.
1724
1725 [RFC4524] Zeilenga, E., Ed., "COSINE LDAP/X.500 Schema", RFC 4524,
1726 June 2006.
1727
1728 [X.500] ITU-T Recommendations X.500 (1993) | ISO/IEC 9594-1:1994,
1729 Information Technology - Open Systems Interconnection -
1730 The Directory: Overview of concepts, models and services.
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768Sciberras Standards Track [Page 31]
1769
1770
1771RFC 4519 LDAP: Schema for User Applications June 2006
1772
1773
1774Appendix A. Changes Made Since RFC 2256
1775
1776 This appendix lists the changes that have been made from RFC 2256 to
1777 RFC 4519.
1778
1779 This appendix is not a normative part of this specification, which
1780 has been provided for informational purposes only.
1781
1782 1. Replaced the document title.
1783
1784 2. Removed the IESG Note.
1785
1786 3. Dependencies on RFC 1274 have been eliminated.
1787
1788 4. Added a Security Considerations section and an IANA
1789 Considerations section.
1790
1791 5. Deleted the conformance requirement for subschema object
1792 classes in favor of a statement in [RFC4517].
1793
1794 6. Added explanation to attribute types and to each object class.
1795
1796 7. Removed Section 4, Syntaxes, and Section 6, Matching Rules,
1797 (moved to [RFC4517]).
1798
1799 8. Removed the certificate-related attribute types:
1800 authorityRevocationList, cACertificate,
1801 certificateRevocationList, crossCertificatePair,
1802 deltaRevocationList, supportedAlgorithms, and userCertificate.
1803
1804 Removed the certificate-related Object Classes:
1805 certificationAuthority, certificationAuthority-V2,
1806 cRLDistributionPoint, strongAuthenticationUser, and
1807 userSecurityInformation
1808
1809 LDAP PKI is now discussed in [RFC4523].
1810
1811 9. Removed the dmdName, knowledgeInformation,
1812 presentationAddress, protocolInformation, and
1813 supportedApplicationContext attribute types and the dmd,
1814 applicationEntity, and dSA object classes.
1815
1816 10. Deleted the aliasedObjectName and objectClass attribute type
1817 definitions. Deleted the alias and top object class
1818 definitions. They are included in [RFC4512].
1819
1820
1821
1822
1823
1824
1825Sciberras Standards Track [Page 32]
1826
1827
1828RFC 4519 LDAP: Schema for User Applications June 2006
1829
1830
1831 11. Added the 'dc' attribute type from RFC 2247, making the
1832 distinction between 'stored' and 'query' values when preparing
1833 IDN strings.
1834
1835 12. Numerous editorial changes.
1836
1837 13. Removed upper bound after the SYNTAX oid in all attribute
1838 definitions where it appeared.
1839
1840 14. Added text about Unicode, SASLprep [RFC4013], and UTF-8 for
1841 userPassword.
1842
1843 15. Included definitions, comments and references for 'dcObject'
1844 and 'uidObject'.
1845
1846 16. Replaced PKI schema references to use RFC 4523.
1847
1848 17. Spelt out and referenced ABNF on first usage.
1849
1850 18. Removed Section 2.4 (Source). Replaced the source table with
1851 explicit references for each definition.
1852
1853 19. All references to an attribute type or object class are
1854 enclosed in single quotes.
1855
1856 20. The layout of attribute type definitions has been changed to
1857 provide consistency throughout the document:
1858 > Section Heading
1859 > Description of Attribute type
1860 > Multivalued description
1861 > Source Information
1862 > Definition
1863 > Example
1864 > Additional Comments
1865
1866 Adding this consistent output included the addition of
1867 examples to some definitions.
1868
1869 21. References to alternate names for attributes types are
1870 provided with a reference to where they were originally
1871 specified.
1872
1873 22. Clarification of the description of 'distinguishedName' and
1874 'name', in regards to these attribute types being supertypes.
1875
1876 23. Spelt out ISDN on first usage.
1877
1878
1879
1880
1881
1882Sciberras Standards Track [Page 33]
1883
1884
1885RFC 4519 LDAP: Schema for User Applications June 2006
1886
1887
1888 24. Inserted a reference to [RFC4517] for the
1889 'teletexTerminalIdentifier' definition's SYNTAX OID.
1890
1891 25. Additional names were added to the IANA Considerations. Names
1892 include 'commonName', 'dcObject', 'domainComponent', 'GN',
1893 'localityName', 'organizationName', 'organizationUnitName',
1894 'surname', 'uidObject' and 'userid'.
1895
1896 26. Renamed all instances of supercede to supersede.
1897
1898 27. Moved [F.1], [F.31] and [RFC4013] from informative to
1899 normative references.
1900
1901 28. Changed the 'c' definition to be consistent with X.500.
1902
1903Author's Address
1904
1905 Andrew Sciberras
1906 eB2Bcom
1907 Suite 3, Woodhouse Corporate Centre,
1908 935 Station Street,
1909 Box Hill North, Victoria 3129
1910 AUSTRALIA
1911
1912 Phone: +61 3 9896 7833
1913 EMail: andrew.sciberras@eb2bcom.com
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939Sciberras Standards Track [Page 34]
1940
1941
1942RFC 4519 LDAP: Schema for User Applications June 2006
1943
1944
1945Full Copyright Statement
1946
1947 Copyright (C) The Internet Society (2006).
1948
1949 This document is subject to the rights, licenses and restrictions
1950 contained in BCP 78, and except as set forth therein, the authors
1951 retain all their rights.
1952
1953 This document and the information contained herein are provided on an
1954 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1955 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1956 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1957 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1958 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1959 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1960
1961Intellectual Property
1962
1963 The IETF takes no position regarding the validity or scope of any
1964 Intellectual Property Rights or other rights that might be claimed to
1965 pertain to the implementation or use of the technology described in
1966 this document or the extent to which any license under such rights
1967 might or might not be available; nor does it represent that it has
1968 made any independent effort to identify any such rights. Information
1969 on the procedures with respect to rights in RFC documents can be
1970 found in BCP 78 and BCP 79.
1971
1972 Copies of IPR disclosures made to the IETF Secretariat and any
1973 assurances of licenses to be made available, or the result of an
1974 attempt made to obtain a general license or permission for the use of
1975 such proprietary rights by implementers or users of this
1976 specification can be obtained from the IETF on-line IPR repository at
1977 http://www.ietf.org/ipr.
1978
1979 The IETF invites any interested party to bring to its attention any
1980 copyrights, patents or patent applications, or other proprietary
1981 rights that may cover technology that may be required to implement
1982 this standard. Please address the information to the IETF at
1983 ietf-ipr@ietf.org.
1984
1985Acknowledgement
1986
1987 Funding for the RFC Editor function is provided by the IETF
1988 Administrative Support Activity (IASA).
1989
1990
1991
1992
1993
1994
1995
1996Sciberras Standards Track [Page 35]
1997
1998
Note: See TracBrowser for help on using the repository browser.