The following examples show more complex user attribute mapping configurations.
The example deployment is a retail clothing company that uses two user directories of different types:
An internal LDAP user directory for employees only.
An ODBC user directory for customers only.
Each user attribute mapping is specific to the user directory for which it is defined.
The following table details how Directory A and Directory B identify the same user information. The accompanying use cases explain how to use different attribute mappings to define a common view of the same user information. The common view serves as a universal schema, which makes the directories operationally identical.
|
Attribute Description |
Directory A Attributes (LDAP) |
Directory B Attributes (ODBC) |
|
First name of each user |
givenname |
u_first_name |
|
Last name of each user |
surname |
u_last_name |
|
Sort name of each user (last name, first name) |
The user directory does not uniquely store the user attribute. |
sort_name |
|
User as a customer |
group:cn=customer,ou=groups,o=acme.com |
Users are always customers. |
|
Status of a user account |
AccountStatus attribute (a set of flags). Second bit is a disabled account. |
u_disabled |
| Copyright © 2012 CA. All rights reserved. |
|