A directory contains data called entries, which contain information about particular objects. Each entry represents one or more objectClasses that defines the type of entry. An objectClass defines the attributes that are associated with it. Therefore, each entry is a collection of attributes with their values, and attributes that belong to the entry depend on the objectClass the entry is based on.
A directory uses a schema for the definitions of objectClasses and attributes. Directories are commonly shipped with a standard set of schema definitions such as country, organization, organizational unit, person, and so on.
You can extend a directory's schema to suit your site's needs by allowing it to recognize and accept the objectClasses and attributes that are used to implement the Advanced Permissions authorization mode for the Notification Website. To allow for customization of directory schemas on-site, it is necessary to avoid any naming conflict among the objects defined by different entities. This is done through the use of guaranteed unique numbers called Object Identifiers (OIDs), each of which unambiguously identifies an objectClass or attribute. These Object Identifiers are guaranteed to be unique across all networks worldwide.
The OIDs form a hierarchy, as shown in the following example:
1 |
ISO- The root authority |
1.3 |
ISO Identified Organization |
1.3.6 |
US Department of Defense |
1.3.6.1 |
Internet OID assignments |
1.3.6.1.4 |
Internet Private |
1.3.6.1.4.1 |
IANA – Registered Private Enterprises |
1.3.6.1.4.1.791 |
CA, Inc. |
The Notification Manager facility is assigned OID 1.3.6.1.4.1.791.2.10.5.3. All OIDs used in our attributes and objectClasses stem from this root OID. This grants unique identification, regardless of what directory product you are using.
Copyright © 2012 CA. All rights reserved. |
|