Connector Guides › Connector Xpress Guide › Creating Connectors › Managing Accounts and Groups › Ambiguous Mappings

Ambiguous Mappings

Connector Xpress supports ambiguous (one-to-many) mappings, which means you can map one provisioning attribute to multiple native attributes.

For example, in an organization where a merge of two employee databases has resulted in a large employee directory, and the employee objects are either an "inetOrgPerson" object or an "account" object, you can ambiguously map the Identity Manager account class to both object classes. As a result, when you search for accounts, the search finds both object types, and you can select which object type you want to use.

At the attribute level, the account class can be represented by only one object class, but a certain value can be populated by one of two attributes. For example, inetOrgPerson has both a postalAddress and a registeredAddress attribute. If some employees have their address saved in postalAddress and other employees in registeredAddress, for example due to a directory merge, you can ambiguously map the Identity Manager address attribute to both of these endpoint attributes and use them interchangeably.