- Title
- Global Address List Schema Mapping Profile
- Description
- Participants within a federation may use different directory representations (Active Directory and IETF schemas) for GAL information, therefore, information within the different directories needs to be mapped to the correct representation for each participant.
Taxonomy
Standards
Guidance
The ‘Contact’ Object Class, defined in Microsoft Active Directory schema, is not a standard LDAP class.
In the case a mapping is required to be performed between the standardised IETF ‘inetOrgPerson’ Object Class and the ‘Contact’ Object Class then the following rules must be applied
- All mandatory attributes in the Consumer object class must be created; and,
- the cardinality of attributes values in the Consumer object class must be maintained (e.g. an attribute may only be allowed a single value in the Consumer’s object class, but the Provider’s object class may allow multiple values).
A potential list of suitable attributes for replication is displayed in the Table. The table provides
- Mappings between the Active Directory and IETF schemas (for those suitable attributes);
Object class the attribute is derived from; and,
- Obligations and cardinality.
The following guide will assist in understanding the table
- “ADUC” - the Active Directory field that is shown in “Active Directory User and Computers” for the attribute (where it exists);
- “Attribute” - the attribute name (which may be different from the LDAP NAME);
- “M” – is the attribute mandatory within the Object Class;
- “OC” – the Object Class with which the attribute is associated; and,
- “Single-Value” – is the attribute single or multi valued.
[CREATE TABLE FROM TABLE 2 IN SIP FOR IDENTITY INFORMATION]