Provisioning - Import users

As part of provisioning users and space templates on a Meeting Server cluster you must define which users to import from the LDAP servers that are connected to the cluster.

On the Provisioning page, Import users tab, you can add user imports, which are sets of LDAP filters and mappings that each define a subset of users to import from one of the connected LDAP servers.

How to add a user import

You can add as many user imports as you like. For each user import, you define subset of users to import from a specific LDAP server, you decide how their username and display names should be created, and you decide if you want to assign them a PMP Plus license.

We recommend that you make sure that the same users are included in only one user import. If PMP licenses are assigned via one user import and not another, and a user matches the LDAP search filter for both user imports, then the user may or may not be assigned a PMP license.

Note: If the same user is included in two different user imports, Meeting Management cannot control which user import the user will be associated with. This means that if a user is included in one user import that assigns PMP Plus licenses to users and is also included in a user import that does not assign any licenses, then you cannot control whether that user is assigned a license.

To define a subset of users to import:

  1. Go to the Servers page and click Set up provisioning.

  2. On the Import users tab, click Add user import.
  3. From the drop-down, choose the LDAP server you want to set this user import filter for.

  4. Enter Base distinguished name.

    The base distinguished name is the starting point for the directory search. The Meeting Server will search for LDAP groups in this node and all nodes below it in the LDAP tree.

    Note: This field is case sensitive.

  5. Enter LDAP search filter.

    This filter defines the subset of users that you want to import.The syntax for the Filter field is described in rfc4515.

    Note: If you are using Active Directory, make sure that you enter a filter that only includes user objects.

  6. Enter Login user name mapping.

    This defines which LDAP attribute you want to use as the username that Meeting Server web app and Meeting App users will use to sign in to the app. It must have a format similar to $sAMAccountName$@example.com, and the attribute must be one that is unique for each user.

    Note: This field is case sensitive.

  7. Enter Display name mapping.

    This is the LDAP attribute that you want to use as participant name in meetings and as contact name in the Meeting App, as well as on each web app user's own Home screen. It must have a format similar to $cn$.

  8. Check the Assign Personal Multiparty Plus (PMP+) license to imported users check box if you want to assign PMP Plus licenses to users who are imported based on these filter settings.

    If you prefer to use SMP Plus licenses, or if you want these users to only join meetings that have a different owner, then leave this check box unchecked.

Note: Your changes will not be applied before you have committed them. After you have committed the changes, template settings will take effect immediately. Changes to LDAP server details and user imports will take effect next time the Meeting Server is synchronized with the LDAP servers.

Note: All changes to provisioning settings that you have entered in Meeting Management will be lost if you restart Meeting Management before the changes have been committed.