Updating Users#

Overview#

Users are typically added or updated on Automate from the sync source, for example, LDAP, CUCM, or CUC. See User Sync Source.

Important

Sync source precedence may override user input. If you update a user on Automate that …

  • Exists on a sync source

  • Has mapped fields

  • Has a higher precedence than LOCAL (Automate) data

Only the mapped fields are updated from the sync source. Data in these fields is updated from the sync source and not the user input added in Automate. These fields are typically read-only in Automate Admin Portal.

For user authentication method (Auth Method) changes when updating, see Authentication Method Setting Rules.

Sync Source Scenarios#

Updating an admin user that has become a subscriber creates a sync with the application highest on the User Sync Source precedence, and according to the field mapping for that source. The sync occurs once you click Save.

Related Topics

Admin User Password Updates#

If the Admin user password is updated, user passwords on CUCM, CUC, and Webex are also updated if these have been provisioned for the user.

Note

Since different UC apps can have different password strictness rules, the update transaction will only succeed if the strictness rules of all the UC apps have been met. Otherwise, the update transaction will roll back.

Administrators should therefore choose a password that meets the requirements of all the UC apps.

User Added as Microsoft Active Directory LDAP User#

If a user was added as a Microsoft Active Directory LDAP user (see: Add Admin Users), then:

  • Additional fields on the User tabs are exposed that can be saved to the Microsoft Active Directory LDAP server.

  • Updates to user details on the LDAP form tab will update the Microsoft Active Directory LDAP server when clicking Save.

  • If user updates made directly on the Microsoft Active Directory LDAP server will reflect on VOSS Automate once the user is again synced in Automate from the Sync & Purge menu.

The table describes additional actions for managing a user. These may be found in the toolbar overflow menu of the Users Page:

Align Hierarchy to Sync Source

For example, if the user’s sync source is CUCM, the data/User is at Customer level, and the CUCM user is at Site level, then the data/User instance will be moved from the Customer level to the CUCM’s hierarchy, that is, to the Site level.

Align Hierarchy to User

All other related instances of the user (e.g. CUCM, device/cucm/User, device/cuc/user, etc.) will be moved to the hierarchy of the data/User instance.

Delete From Ldap

Relevant only for Microsoft Active Directory LDAP server. The delete transaction succeeds only for users on Microsoft Active Directory LDAP servers on port 636, where the Enable Write Operations setting is checked. Thus, if Write operations are enabled on the associated LDAP server and the LDAP server is a secured Active Directory LDAP server, the LDAP user (device/ldap/user) is removed, and the VOSS user (data/User) is updated, that is, the sync type (source) is set to LOCAL to reflect LDAP removal.

See also, Add Admin Users

If there is an associated CUCM user, the CUCM user and the VOSS user are updated. In this case:

  • The CUCM user is converted to a non-LDAP user and the LDAP directory name is removed (set to clear)

  • The VOSS user’s (data/User) sync type is updated to CUCM-Local.

Push To Ldap

Creates an LDAP user (if the LDAP user does not exist). Requires availability of an LDAP server that allows write back and is configured as a secure Microsoft Active Directory server. This server must be on port 636, with Enable Write Operations checked.

Used when adding user details on the LDAP form tab for the first time and first adding the LDAP user. See Add Admin Users. Clicking the Save button when you’re done also updates the LDAP user details on the LDAP server. However, if any user details have been updated for the LDAP server, this Push To Ldap menu option will also save these.

On the Users list view (default menu, User Management > Users):

  1. Click on a non-LDAP user you wish to push to LDAP.

  2. On the LDAP tab/panel, choose the LDAP server, fill out a description and password.

  3. Click Action > Push to LDAP. The LDAP user is created on the selected LDAP server.

This menu option can’t be used for Automate LDAP-synced users (in which case a system message on the LDAP tab displays the following error message: Push to LDAP is not allowed).

Related Topics