These are the Object Classes that are being used in the UVM LDAP Directory
Server but were not developed here.
inetOrgPerson inherits all the attributes of these two:
| Attribute Name |
Description |
|---|---|
| eduPersonAffiliation |
Specifies the person's relationship(s) to the institution
in broad categories such as student, faculty, staff, alum, etc |
| eduPersonNickname |
Person's nickname, or the informal name by which
they are accustomed to be hailed |
| eduPersonOrgDN |
The distinguished name (DN) of the directory entry
representing the institution with which the person is associated |
| eduPersonOrgUnitDN |
The distinguished name (DN) of the directory entries
representing the person's Organizational Unit(s) |
| eduPersonPrimaryAffiliation |
Specifies the person's PRIMARY relationship to the
institution in broad categories such as student, faculty, staff, alum, etc |
| eduPersonPrincipalName |
The "NetID" of the person for the purposes of inter-institutional
authentication. Should be stored in the form of user@univ.edu, where univ.edu
is the name of the local security domain |
| eduPersonEntitlement |
URI (either URN or URL) that indicates a set of
rights to specific resources |
| eduPersonPrimaryOrgUnitDN |
The distinguished name (DN) of the directory entries
representing the person's primary Organizational Unit |
None.
| Attribute |
Description |
|---|---|
| mailLocalAddress |
RFC822 email address of this recipient (such as Frank.Swasey@uvm.edu) |
| mailHost |
Fully qualified domain name (FQDN) of the mail server
for this recipient |
| mailRoutingAddress |
RFC822 routing address of this recipient (such as
fcs@zoo.uvm.edu) |
None.
| Attribute |
Description |
|---|---|
| audio |
The Audio attribute type allows the storing of sounds
in the Directory. The attribute uses a u-law encoded sound file as used by
the "play" utility on a Sun 4. This is an interim format. |
| businessCategory |
This attribute describes the kind of business performed
by an organization. |
| carLicense |
This multivalued field is used to record the values
of the license or registration plate associated with an individual |
| departmentNumber |
Code for department to which a person belongs. This
can also be strictly numeric (e.g., 1234) or alphanumeric (e.g., ABC/123) |
| displayName |
When displaying an entry, especially within a one-line
summary list, it is useful to be able to identify a name to be used. Since
other attribute types such as 'cn' are multivalued, an additional attribute
type is needed. Display name is defined for this purpose. |
| employeeNumber |
Numeric or alphanumeric identifier assigned to a
person, typically based on order of hire or association with an organization.
Single valued. |
| employeeType |
Used to identify the employer to employee relationship. Typical values used will be "Contractor", "Employee", "Intern", "Temp", "External", and "Unknown" but any value may be used. |
| givenName (gn) |
used to hold the part of a person's name which is not their surname nor middle name |
| homePhone (homeTelephoneNumber) |
The Home Telephone Number attribute type specifies a home telephone number associated with a person. Attribute values should follow the agreed format for international telephone numbers: i.e., "+44 71 123 4567". |
| homePostalAddress |
The Home postal address attribute type specifies a home postal address for an object. This should be limited to up to 6 lines of 30 characters each. |
| initials |
contains the initials of some or all of an individuals names, but not the surname(s) |
| jpegPhoto |
Used to store one or more images of a person using the JPEG File Interchange Format [JFIF]. Note that the jpegPhoto attribute type was defined for use in the Internet X.500 pilots but no referencable definition for it could be located. |
| labeledURI |
RFC2079: Uniform Resource Identifier with optional label |
| mail (rfc822Mailbox) |
RFC1274: RFC822 Mailbox |
| manager |
The Manager attribute type specifies the manager of an object represented by an entry. The attribute value for Manager is a distinguished name. |
| mobile (mobileTelephoneNumber) |
The Mobile Telephone Number attribute type specifies a mobile telephone number associated with a person. Attribute values should follow the agreed format for international telephone numbers: i.e., "+44 71 123 4567". |
| o (organizationName) |
the name of an organization |
| pager (pagerTelephoneNumber) |
The Pager Telephone Number attribute type specifies a pager telephone number for an object. Attribute values should follow the agreed format for international telephone numbers: i.e., "+44 71 123 4567". |
| photo |
The Photo attribute type specifies a "photograph" for an object. This should be encoded in G3 fax. |
| roomNumber |
The Room Number attribute type specifies the room number of an object. Note that the commonName attribute should be used for naming room objects. |
| secretary |
The Secretary attribute type specifies the secretary
of a person. The attribute value for Secretary is a distinguished name. |
| uid (userid) |
The Userid attribute type specifies a computer system login name. |
| userCertificate |
This is the preferred attribute to store the S/MIME
certificate in. It must be stored and requested in the binary form,
as 'userCertificate;binary' |
| x500uniqueIdentifier |
The x500UniqueIdentifier attribute is used to distinguish between objects when a distinguished name has been reused. This is a different attribute type from both the "uid" and "uniqueIdentifier" types. |
| preferredLanguage |
Used to indicate an individual's preferred written or spoken language. This is useful for international correspondence or human-computer interaction. Values for this attribute type MUST conform to the definition of the Accept-Language header field defined in [RFC2068] with one exception: the sequence "Accept-Language" ":" should be omitted. This is a single valued attribute type. |
| userSMIMECertificate |
A PKCS#7 [RFC2315] SignedData, where the content
that is signed is ignored by consumers of userSMIMECertificate values.
It is recommended that values have a `contentType' of data with an
absent `content' field. Values of this attribute contain a person's entire
certificate chain and an smimeCapabilities field [RFC2633] that at a minimum
describes their SMIME algorithm capabilities. Values for this attribute
are to be stored and requested in binary form, as 'userSMIMECertificate;binary'.
If available, this attribute is preferred over the userCertificate attribute
for S/MIME applications. OpenLDAP note: ";binary" transfer should NOT be used as syntax is binary |
| userPKCS12 |
PKCS #12 [PKCS12] provides a format for exchange
of personal identity information. When such information is stored in a directory
service, the userPKCS12 attribute should be used. This attribute is to be
stored and requested in binary form, as 'userPKCS12;binary'. The attribute
values are PFX PDUs stored as binary data. OpenLDAP note: ";binary" transfer should NOT be used as syntax is binary |
None.
| Attribute |
Description |
|---|---|
| title |
The title, such as "Vice President", of a person in their organizational context. |
| x121Address |
No Description Available.... |
| registeredAddress |
This attribute holds a postal address suitable for reception of telegrams or expedited documents, where it is necessary to have the recipient accept delivery. |
| destinationIndicator |
This attribute is used for the telegram service. |
| preferredDeliveryMethod |
The preferred delivery method. Valid values
are: "any" / "mhs" / "physical" / "telex" / "teletex" / "g3fax" / "g4fax"
/ "ia5" / "videotex" / "telephone" (Single Valued) |
| telexNumber |
The telex number in the international notation Example: 817379, ch, ehhg |
| teletexTerminalIdentifier |
No Description Available.... |
| telephoneNumber |
The phone number in the international notation according to CCITT E.123. The separator '-' instead of space may be used according to the local habit, it should be used consistently within a country. |
| internationaliSDNNumber |
No Description Available.... No, iSDN is not a typo :-) |
| facsimileTelephoneNumber (fax) |
The phone number in the international notation according to CCITT E.123. The separator `-` instead of space may be used according to the local habit, it should be used consistently within a country. |
| street (streetAddress) |
This attribute contains the physical address of the object to which the entry corresponds, such as an address for package delivery (streetAddress). It shall be the street where the person has its office. Mostly, it will be the street part of the postalAddress. |
| postOfficeBox |
No Description Available... One would
assume; however; that this is your Post Office Box number. |
| postalCode |
The postalCode will be the same as used in the postalAddress (i international notation). |
| postalAddress |
The full postal address (but not including the name) in international notation, with up to 6 lines with 30 characters each. |
| physicalDeliveryOfficeName |
No Description Available... |
| ou (organizationalUnitName) |
This attribute contains the name of an organizational unit (organizationalUnitName). The name of a part of the organisation. Additional names like abbreviations should be provided for better search results. |
| st (stateOrProvinceName) |
This attribute contains the full name of a state
or province (stateOrProvinceName). Name of the canton, county, department, province or state with values in local and other languages as useful. If official and commonly used abbreviations exist for the states, they should be supplied as additional values |
| l (localityName) |
This attribute contains the name of a locality, such as a city, county or other geographic region. |
None.
| Attribute |
Description |
|---|---|
| sn (surname) |
This is the X.500 surname attribute, which contains
the family name of a person. |
| cn (commonName) |
This is the X.500 commonName attribute, which contains a name of an object. If the object corresponds to a person, it is typically the person's full name. |
| userPassword |
from earlier rfc2256: Passwords are stored using an Octet String syntax and are not encrypted. Transfer of cleartext passwords are strongly discouraged where the underlying transport service cannot guarantee confidentiality and may result in disclosure of the password to unauthorized parties. from later rfc2307 An entry of class posixAccount, posixGroup, or shadowAccount without A userPassword attribute MUST NOT be used for authentication. The client should be returned a non-matchable password such as "x". userPassword values MUST be represented by following syntax:
The encrypted password contains of a plaintext key hashed using the algorithm scheme. userPassword values which do not adhere to this syntax MUST NOT be used for authentication. The DUA MUST iterate through the values of the attribute until a value matching the above syntax is found. Only if encryptedpassword is an empty string does the user have no password. DUAs are not required to consider encryption schemes which the client will not recognize; in most cases, it may be sufficient to consider only "crypt". Note: OpenLDAP supports a scheme of KERBEROS, which UVM is using. |
| telephoneNumber |
The phone number in the international notation according to CCITT E.123. The separator '-' instead of space may be used according to the local habit, it should be used consistently within a country. |
| seeAlso |
Reference to another closely related entry in the DIT, e.g., from a room to the person using that room. It is the Distinguished Name of the entry. |
| description |
This attribute contains a human-readable description
of the object. A short informal explanation of special interests of a person or organisation. Overlap with businessCategory, organizationalStatus and title should be avoided. |
sn, cn
Last modified December 03 2002 04:00 PM
