Redbrick User management tool
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

156 lines
6.2 KiB

  1. # inetorgperson.schema -- InetOrgPerson (RFC2798)
  2. # $OpenLDAP: pkg/ldap/servers/slapd/schema/inetorgperson.schema,v 1.14.4.3 2005/01/20 17:01:18 kurt Exp $
  3. ## This work is part of OpenLDAP Software <http://www.openldap.org/>.
  4. ##
  5. ## Copyright 1998-2005 The OpenLDAP Foundation.
  6. ## All rights reserved.
  7. ##
  8. ## Redistribution and use in source and binary forms, with or without
  9. ## modification, are permitted only as authorized by the OpenLDAP
  10. ## Public License.
  11. ##
  12. ## A copy of this license is available in the file LICENSE in the
  13. ## top-level directory of the distribution or, alternatively, at
  14. ## <http://www.OpenLDAP.org/license.html>.
  15. #
  16. # InetOrgPerson (RFC2798)
  17. #
  18. # Depends upon
  19. # Definition of an X.500 Attribute Type and an Object Class to Hold
  20. # Uniform Resource Identifiers (URIs) [RFC2079]
  21. # (core.schema)
  22. #
  23. # A Summary of the X.500(96) User Schema for use with LDAPv3 [RFC2256]
  24. # (core.schema)
  25. #
  26. # The COSINE and Internet X.500 Schema [RFC1274] (cosine.schema)
  27. # carLicense
  28. # This multivalued field is used to record the values of the license or
  29. # registration plate associated with an individual.
  30. attributetype ( 2.16.840.1.113730.3.1.1
  31. NAME 'carLicense'
  32. DESC 'RFC2798: vehicle license or registration plate'
  33. EQUALITY caseIgnoreMatch
  34. SUBSTR caseIgnoreSubstringsMatch
  35. SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
  36. # departmentNumber
  37. # Code for department to which a person belongs. This can also be
  38. # strictly numeric (e.g., 1234) or alphanumeric (e.g., ABC/123).
  39. attributetype ( 2.16.840.1.113730.3.1.2
  40. NAME 'departmentNumber'
  41. DESC 'RFC2798: identifies a department within an organization'
  42. EQUALITY caseIgnoreMatch
  43. SUBSTR caseIgnoreSubstringsMatch
  44. SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
  45. # displayName
  46. # When displaying an entry, especially within a one-line summary list, it
  47. # is useful to be able to identify a name to be used. Since other attri-
  48. # bute types such as 'cn' are multivalued, an additional attribute type is
  49. # needed. Display name is defined for this purpose.
  50. attributetype ( 2.16.840.1.113730.3.1.241
  51. NAME 'displayName'
  52. DESC 'RFC2798: preferred name to be used when displaying entries'
  53. EQUALITY caseIgnoreMatch
  54. SUBSTR caseIgnoreSubstringsMatch
  55. SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
  56. SINGLE-VALUE )
  57. # employeeNumber
  58. # Numeric or alphanumeric identifier assigned to a person, typically based
  59. # on order of hire or association with an organization. Single valued.
  60. attributetype ( 2.16.840.1.113730.3.1.3
  61. NAME 'employeeNumber'
  62. DESC 'RFC2798: numerically identifies an employee within an organization'
  63. EQUALITY caseIgnoreMatch
  64. SUBSTR caseIgnoreSubstringsMatch
  65. SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
  66. SINGLE-VALUE )
  67. # employeeType
  68. # Used to identify the employer to employee relationship. Typical values
  69. # used will be "Contractor", "Employee", "Intern", "Temp", "External", and
  70. # "Unknown" but any value may be used.
  71. attributetype ( 2.16.840.1.113730.3.1.4
  72. NAME 'employeeType'
  73. DESC 'RFC2798: type of employment for a person'
  74. EQUALITY caseIgnoreMatch
  75. SUBSTR caseIgnoreSubstringsMatch
  76. SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
  77. # jpegPhoto
  78. # Used to store one or more images of a person using the JPEG File
  79. # Interchange Format [JFIF].
  80. # Note that the jpegPhoto attribute type was defined for use in the
  81. # Internet X.500 pilots but no referencable definition for it could be
  82. # located.
  83. attributetype ( 0.9.2342.19200300.100.1.60
  84. NAME 'jpegPhoto'
  85. DESC 'RFC2798: a JPEG image'
  86. SYNTAX 1.3.6.1.4.1.1466.115.121.1.28 )
  87. # preferredLanguage
  88. # Used to indicate an individual's preferred written or spoken
  89. # language. This is useful for international correspondence or human-
  90. # computer interaction. Values for this attribute type MUST conform to
  91. # the definition of the Accept-Language header field defined in
  92. # [RFC2068] with one exception: the sequence "Accept-Language" ":"
  93. # should be omitted. This is a single valued attribute type.
  94. attributetype ( 2.16.840.1.113730.3.1.39
  95. NAME 'preferredLanguage'
  96. DESC 'RFC2798: preferred written or spoken language for a person'
  97. EQUALITY caseIgnoreMatch
  98. SUBSTR caseIgnoreSubstringsMatch
  99. SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
  100. SINGLE-VALUE )
  101. # userSMIMECertificate
  102. # A PKCS#7 [RFC2315] SignedData, where the content that is signed is
  103. # ignored by consumers of userSMIMECertificate values. It is
  104. # recommended that values have a `contentType' of data with an absent
  105. # `content' field. Values of this attribute contain a person's entire
  106. # certificate chain and an smimeCapabilities field [RFC2633] that at a
  107. # minimum describes their SMIME algorithm capabilities. Values for
  108. # this attribute are to be stored and requested in binary form, as
  109. # 'userSMIMECertificate;binary'. If available, this attribute is
  110. # preferred over the userCertificate attribute for S/MIME applications.
  111. ## OpenLDAP note: ";binary" transfer should NOT be used as syntax is binary
  112. attributetype ( 2.16.840.1.113730.3.1.40
  113. NAME 'userSMIMECertificate'
  114. DESC 'RFC2798: PKCS#7 SignedData used to support S/MIME'
  115. SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
  116. # userPKCS12
  117. # PKCS #12 [PKCS12] provides a format for exchange of personal identity
  118. # information. When such information is stored in a directory service,
  119. # the userPKCS12 attribute should be used. This attribute is to be stored
  120. # and requested in binary form, as 'userPKCS12;binary'. The attribute
  121. # values are PFX PDUs stored as binary data.
  122. ## OpenLDAP note: ";binary" transfer should NOT be used as syntax is binary
  123. attributetype ( 2.16.840.1.113730.3.1.216
  124. NAME 'userPKCS12'
  125. DESC 'RFC2798: personal identity information, a PKCS #12 PFX'
  126. SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
  127. # inetOrgPerson
  128. # The inetOrgPerson represents people who are associated with an
  129. # organization in some way. It is a structural class and is derived
  130. # from the organizationalPerson which is defined in X.521 [X521].
  131. objectclass ( 2.16.840.1.113730.3.2.2
  132. NAME 'inetOrgPerson'
  133. DESC 'RFC2798: Internet Organizational Person'
  134. SUP organizationalPerson
  135. STRUCTURAL
  136. MAY (
  137. audio $ businessCategory $ carLicense $ departmentNumber $
  138. displayName $ employeeNumber $ employeeType $ givenName $
  139. homePhone $ homePostalAddress $ initials $ jpegPhoto $
  140. labeledURI $ mail $ manager $ mobile $ o $ pager $
  141. photo $ roomNumber $ secretary $ uid $ userCertificate $
  142. x500uniqueIdentifier $ preferredLanguage $
  143. userSMIMECertificate $ userPKCS12 )
  144. )