User Field Mapping¶
Choose the User Field Mapping menu to see the list of mappings at a hierarchy.
VOSS-4-UC provides a set of default (name is default
) field mappings between applications and
VOSS-4-UC user data at the sys
level hierarchy.
These mappings are used to align data during sync operations.
Whenever an application is added at a hierarchy, the default application mapping is cloned to this hierarchy level and provided with an application name (e.g. IP address for Unified CM, business key for LDAP server). This cloned mapping shows in the User Field Mapping list and applies to user management at this hierarchy.
Important
While many fields in the hierarchy-specific field mapping can be edited, care should be taken when modifying these mappings. A change will only apply to the management of new users, in other words existing user data at this hierarchy will not be affected by these mapping changes.
Data alignment means that the mapping that applies at the sync hierarchy
for an application which is the sync source will be used when values are
written to VOSS-4-UC user data. The mapping is stored in the data/UserFieldMapping
model.
The applications are:
Application Name | Model Type |
---|---|
CUC | device/cuc/User |
CUCM | device/cucm/User |
HCMF | device/hcmf/User |
LOCAL | data/User |
MS_LDAP | device/ldap/user |
OPEN_LDAP | device/ldap/InetOrgPerson |
CCX | device/uccx/Agent |
WEBEX_TEAMS | device/spark/User |
For example, the default CUCM mapping contains the mapping:
VOSS-4-UC | CUCM |
---|---|
User Name | userid |
Upon a sync of user data from a Unified CM source, where this default
CUCM mapping applies at the hierarchy, the sync will
update the VOSS-4-UC user on the list available from the Users menu. The user’s Sync Source
value shows as CUCM
.
Important
If application users related to a custom field mapping exist in VOSS-4-UC, the fields that are already mapped cannot be modified. The fields are marked read-only on the interface.
In addition, 10 customizable of values of the following types are available that can also be mapped:
- Custom String
- Custom List of Strings
- Custom Boolean
After the sync, the custom values are then shown on the Custom tab of an entry on the User menu.
LDAP Mappings¶
- LDAP Username
- For Microsoft Active Directory, this is typically the
sAMAccountName
. - For AD LDS (ADAM), the
sAMAccountName
attribute is not part of the default schema, but can be added if required. Confirm with the LDAP server administrator. Alternatively, useuid
. - For OpenLDAP, this is typically the
uid
.
- For Microsoft Active Directory, this is typically the
- Sn (Surname)