Introduction to User Management in VOSS Automate¶
Overview¶
VOSS Automate supports two types of users:
Administrators |
Can be assigned to any of the hierarchy nodes (provider, customer, site). |
End users |
Can be created at any level of the hierarchy, but can only become subscribers at the site level. |
Important
When upgrading from 19.X or earlier, please refer to the VOSS-4-UC 21.1 Release Changes and Impact PDF document on the Documentation Portal for details on model and workflow changes in 21.1 / 21.2. Customizations related to these changes may be affected.
How Users are Added to the System¶
Users may be added to VOSS Automate from these sources:
Synchronized from LDAP
Synchronized from CUCM (Cisco Unified Communications Manager)
Synchronized from Azure (Microsoft users)
Bulk loaded, via a Bulk loader template
Manually created
Note
Conflicts between users synchronized from different sources are handled according to the strategy described in Managing Duplicate Usernames. For information about user password management, depending on the source of the user, see Password Management.
Users are typically associated with a site. You can create move filters to automatically assign users to sites once they are synchronized from LDAP or from CUCM. Bulk loaded and manually created users can be moved using filters or by individually selecting users.
Cisco users associated with a site can be added to the CUCM that appears in the network device list (NDL) assigned to that site. When a Cisco user is added to CUCM, it becomes a subscriber, and can be provisioned with various collaboration services.
For details around how Microsoft users are synced in from Azure and then moved to the sites as subscribers, see Microsoft Subscribers
User Authentication¶
Authentication (auth) methods define how a user is authenticated when logging in to VOSS Automate, either Automatic, LDAP, SSO, or Local.
If an identity provider (IdP) server is deployed at a hierarchy node above the site, you can configure VOSS Automate to provide single sign-on (SSO) support for users created or synchronized at that hierarchy node.
Note
Typically, Microsoft users will not need to log in to VOSS Automate. Their default auth method is Automatic. When the default auth method is set to LDAP, VOSS Automate checks with the LDAP server to verify the user’s credentials. Once verified, the user is logged in to VOSS Automate.
User Default Language¶
If a user’s language is not explicitly set, the language is inherited from the nearest hierarchy node (at or above the user node) that has a default language. If no default language is set anywhere in the hierarchy at or above the user node, the language is set to English.
Related Topics