3. Unit Entries at oakUnitCode=code,ou=units,dc=oak,dc=ox,dc=ac,dc=uk

Entries here represent organisational units. Many of these are organisational units of the University of Oxford, such as departments and colleges.

3.1. Example Entry

dn: oakUnitCode=oucs,ou=units,dc=oak,dc=ox,dc=ac,dc=uk
cn: Computing Services
displayName: Computing Services
facsimileTelephoneNumber: +44 1865 273275
member: oakPrimaryPersonID=38463,ou=people,dc=oak,dc=ox,dc=ac,dc=uk
member: oakPrimaryPersonID=6075,ou=people,dc=oak,dc=ox,dc=ac,dc=uk
member: oakPrimaryPersonID=21139,ou=people,dc=oak,dc=ox,dc=ac,dc=uk
member: oakPrimaryPersonID=6423,ou=people,dc=oak,dc=ox,dc=ac,dc=uk
oakDivision: acserv
oakSuperUnit: it
oakUnitCode: oucs
oakUnitStatus: department
oakUnitURI: http://www.oucs.ox.ac.uk/
objectClass: oakOrganizationalUnit
ou: Computing Services
postalAddress: 13 Banbury Road, Oxford, OX2 6NN
telephoneNumber: +44 1865 273200

3.2. cn Attribute Type

This standard attribute type is defined in the following places:

This attribute type's matching rule makes it case insensitive.

3.2.1. Example

cn: Computing Services

3.2.2. Release Policy

  • everyone can perform read operations

3.3. displayName Attribute Type

This standard attribute type is defined in the following places:

This attribute type's matching rule makes it case sensitive.

3.3.1. Example

displayName: Computing Services

3.3.2. Release Policy

  • everyone can perform read operations

3.4. facsimileTelephoneNumber Attribute Type

This standard attribute type is defined in the following places:

3.4.1. Example

facsimileTelephoneNumber: +44 1865 273275

3.4.2. Release Policy

  • all service providers can perform read operations

3.5. member Attribute Type

This standard attribute type is defined in the following places:

Because this attribute type holds a distinguished name (matching rule), some components may be case sensitive and some may be case insensitive.

3.5.1. Example

member: oakPrimaryPersonID=38463,ou=people,dc=oak,dc=ox,dc=ac,dc=uk
member: oakPrimaryPersonID=6075,ou=people,dc=oak,dc=ox,dc=ac,dc=uk
member: oakPrimaryPersonID=21139,ou=people,dc=oak,dc=ox,dc=ac,dc=uk
member: oakPrimaryPersonID=6423,ou=people,dc=oak,dc=ox,dc=ac,dc=uk

3.5.2. Release Policy

  • all service providers can perform read operations

3.6. oakDivision Attribute Type

This attribute type's matching rule makes it case insensitive.

3.6.1. Example

oakDivision: acserv

3.6.2. OpenLDAP-Compatible Attribute Type Declaration

This is a locally-defined attribute type. Its definition from the schema follows, in an OpenLDAP-Compatible format.

attributeType ( 1.3.6.1.4.1.11023.1.1.7.2.1.17
    NAME          'oakDivision'
    DESC          'Oxford Division'
    SYNTAX        1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
    EQUALITY      caseIgnoreMatch
    SUBSTR        caseIgnoreSubstringsMatch
 )

3.6.3. Release Policy

  • everyone can perform read operations

3.7. oakSuperUnit Attribute Type

This attribute type's matching rule makes it case insensitive.

3.7.1. Example

oakSuperUnit: it

3.7.2. OpenLDAP-Compatible Attribute Type Declaration

This is a locally-defined attribute type. Its definition from the schema follows, in an OpenLDAP-Compatible format.

attributeType ( 1.3.6.1.4.1.11023.1.1.7.2.1.16
    NAME          'oakSuperUnit'
    DESC          'Oxford Super Unit'
    SYNTAX        1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
    EQUALITY      caseIgnoreMatch
    SUBSTR        caseIgnoreSubstringsMatch
 )

3.7.3. Release Policy

  • everyone can perform read operations

3.8. oakUnitCode Attribute Type

This attribute type's matching rule makes it case sensitive.

3.8.1. Example

oakUnitCode: oucs

3.8.2. OpenLDAP-Compatible Attribute Type Declaration

This is a locally-defined attribute type. Its definition from the schema follows, in an OpenLDAP-Compatible format.

attributeType ( 1.3.6.1.4.1.11023.1.1.7.2.1.23
    NAME          'oakUnitCode'
    DESC          'Unit Code'
    SYNTAX        1.3.6.1.4.1.1466.115.121.1.15
    EQUALITY      caseExactMatch
 )

3.8.3. Release Policy

  • everyone can perform read operations

3.9. oakUnitStatus Attribute Type

Status of the Unit. The possible values, with their meanings, are:
college
the unit is a college of the collegiate University of Oxford
department
the unit is a department of the University of Oxford
If this attribute is not present, nothing from the above list is being asserted by Oak LDAP. New possible values may be added for this attribute in future.

3.9.1. Example

oakUnitStatus: department

3.9.2. OpenLDAP-Compatible Attribute Type Declaration

This is a locally-defined attribute type. Its definition from the schema follows, in an OpenLDAP-Compatible format.

attributeType ( 1.3.6.1.4.1.11023.1.1.7.2.1.51
    NAME          'oakUnitStatus'
    DESC          'Unit Status'
    SYNTAX        1.3.6.1.4.1.1466.115.121.1.15
    EQUALITY      caseIgnoreMatch
    SUBSTR        caseIgnoreSubstringsMatch
 )

3.9.3. Release Policy

  • everyone can perform read operations

3.10. oakUnitURI Attribute Type

This attribute type's matching rule makes it case sensitive.

3.10.1. Example

oakUnitURI: http://www.oucs.ox.ac.uk/

3.10.2. OpenLDAP-Compatible Attribute Type Declaration

This is a locally-defined attribute type. Its definition from the schema follows, in an OpenLDAP-Compatible format.

attributeType ( 1.3.6.1.4.1.11023.1.1.7.2.1.18
    NAME          'oakUnitURI'
    DESC          'Uniform Resource Identifier'
    SYNTAX        1.3.6.1.4.1.1466.115.121.1.15
    EQUALITY      caseExactMatch
 )

3.10.3. Release Policy

  • everyone can perform read operations

3.11. objectClass Attribute Type

This standard attribute type is defined in the following places:

This attribute type's matching rule (see also RFC 4512 section-1.4 ) makes it case insensitive.

3.11.1. Example

objectClass: oakOrganizationalUnit

3.11.2. Release Policy

  • everyone can perform read operations

3.12. ou Attribute Type

This standard attribute type is defined in the following places:

This attribute type's matching rule makes it case insensitive.

3.12.1. Example

ou: Computing Services

3.12.2. Release Policy

  • everyone can perform read operations

3.13. postalAddress Attribute Type

This standard attribute type is defined in the following places:

This attribute type's matching rule makes it case insensitive.

3.13.1. Example

postalAddress: 13 Banbury Road, Oxford, OX2 6NN

3.13.2. Release Policy

  • all service providers can perform read operations

3.14. telephoneNumber Attribute Type

This standard attribute type is defined in the following places:

3.14.1. Example

telephoneNumber: +44 1865 273200

3.14.2. Release Policy

  • all service providers can perform read operations

Up: Contents Previous: 2. Person Entries at oakPrimaryPersonID=id,ou=people,dc=oak,dc=ox,dc=ac,dc=uk Next: 4. Principal Entries at krbPrincipalName=princname,cn=OX.AC.UK,cn=KerberosRealms,dc=oak,dc=ox,dc=ac,dc=uk