6.3. About Synchronized Attributes
Identity Management synchronizes a subset of user attributes between IdM and Active Directory user entries. Any other attributes present in the entry, either in Identity Management or in Active Directory, are ignored by synchronization.
Most POSIX attributes are not synchronized.
Although there are significant schema differences between the Active Directory LDAP schema and the 389 Directory Server LDAP schema used by Identity Management, there are many attributes that are the same. These attributes are simply synchronized between the Active Directory and IdM user entries, with no changes to the attribute name or value format.
User Schema That Are the Same in Identity Management and Windows Servers
Some attributes have different names but still have direct parity between IdM (which uses 389 Directory Server) and Active Directory. These attributes are mapped by the synchronization process.
Table 6.2. User Schema Mapped between Identity Management and Active Directory
|Identity Management||Active Directory|
6.3.1. User Schema Differences between Identity Management and Active Directory
Even though attributes may be successfully synchronized between Active Directory and IdM, there may still be differences in how Active Directory and Identity Management define the underlying X.500 object classes. This could lead to differences in how the data are handled in the different LDAP services.
This section describes the differences in how Active Directory and Identity Management handle some of the attributes which can be synchronized between the two domains.
188.8.131.52. Values for cn Attributes
In 389 Directory Server, the
cnattribute can be multi-valued, while in Active Directory this attribute must have only a single value. When the Identity Management
cnattribute is synchronized, then, only one value is sent to the Active Directory peer.
What this means for synchronization is that, potentially, if a
cnvalue is added to an Active Directory entry and that value is not one of the values for
cnin Identity Management, then all of the Identity Management
cnvalues are overwritten with the single Active Directory value.
One other important difference is that Active Directory uses the
cnattribute as its naming attribute, where Identity Management uses
uid. This means that there is the potential to rename the entry entirely (and accidentally) if the
cnattribute is edited in the Identity Management.
184.108.40.206. Values for street and streetAddress
Active Directory uses the attribute
streetAddressfor a user's postal address; this is the way that 389 Directory Server uses the
streetattribute. There are two important differences in the way that Active Directory and Identity Management use the
- In 389 Directory Server,
streetAddressis an alias for
street. Active Directory also has the
streetattribute, but it is a separate attribute that can hold an independent value, not an alias for
- Active Directory defines both
streetas single-valued attributes, while 389 Directory Server defines
streetas a multi-valued attribute, as specified in RFC 4519.
Because of the different ways that 389 Directory Server and Active Directory handle
streetattributes, there are two rules to follow when setting address attributes in Active Directory and Identity Management:
- The synchronization process maps
streetAddressin the Active Directory entry to
streetin Identity Management. To avoid conflicts, the
streetattribute should not be used in Active Directory.
- Only one Identity Management
streetattribute value is synchronized to Active Directory. If the
streetAddressattribute is changed in Active Directory and the new value does not already exist in Identity Management, then all
streetattribute values in Identity Management are replaced with the new, single Active Directory value.
220.127.116.11. Constraints on the initials Attribute
initialsattribute, Active Directory imposes a maximum length constraint of six characters, but 389 Directory Server does not have a length limit. If an
initialsattribute longer than six characters is added to Identity Management, the value is trimmed when it is synchronized with the Active Directory entry.
18.104.22.168. Requiring the surname (sn) Attribute
Active Directory allows
personentries to be created without a surname attribute. However, RFC 4519 defines the
personobject class as requiring a surname attribute, and this is the definition used in Directory Server.
If an Active Directory
personentry is created without a surname attribute, that entry will not be synchronized over to IdM since it fails with an object class violation.
6.3.2. Active Directory Entries and POSIX Attributes
When a Windows user account contains values for the
gidNumberattributes, WinSync does not synchronize these values over to Identity Management. Instead, it creates new UID and GID values in Identity Management.
As a result, the values for
gidNumberare different in Active Directory and in Identity Management.
cnis treated differently than other synchronized attributes. It is mapped directly (
cn) when synchronizing from Identity Management to Active Directory. When synchronizing from Active Directory to Identity Management, however,
cnis mapped from the
nameattribute on Windows to the
cnattribute in Identity Management.