Below are sample settings for an IDS connection to CloudLink Platform.
The following features are not supported with CloudLink IDS:
• External Search
• External Reverse Lookup
• Search Context, i.e., OU based search
• Query String i.e. all users synced on CloudLink from Azure would be synced on MiCollab
CloudLink IDS connection has a functionality called, Re-initialize on next cycle, where the Administrator can re-initialize all user sync from CloudLink. This option effectively forces a full synchronization on the next scheduled sync event. A full synchronization queries the directory server for the entire set of users. This option can be used to recover the MiCollab database from the directory server. It will most likely result in a large number of detained user updates.
Prior to the enabling of CloudLink-based Integration on MiCollab you will notice that there are only four Directory Server types under Integrated Directory Services:
• Active Directory
• MiVoice 5000 / MiVoice 5000 Manager
• Generic LDAP
• ForgeRock Directory Services
If CloudLink Integration is enabled, CloudLink Platform will be shown under available Directory Server Types. Refer from step 6 onwards for further configuration.
If CloudLink Integration is not enabled, then the following steps will be required to enable CloudLink on MiCollab.
From Configuration > MiCollab Settings proceed to the CloudLink Integration tab.
Check the box I agree to the Mitel Cloud Services Terms and Conditions and then click the Connect CloudLink button.
MiCollab will indicate: You are being directed to Mitel Auth Portal for additional authentication. Make sure your web browser pop-up blocker is disabled. Do you want to proceed?
Click OK to proceed.
As a CloudLink Accounts Console user administrator you will be asked by CloudLink to:
Enter your username (email address)
Enter your password
NOTE: It is assumed that CloudLink has already been setup to include a user (administrator) and an account (customer).
Any users that exist on MiCollab will be sent to CloudLink. This can be confirmed by looking at the users on CloudLink and comparing them with MiCollab.
NOTE: At this point CloudLink-based Authentication has not been enabled.
5. Return to Configuration > Integrated Directory Services and click Add Connection.
When the new connection page is provided, select the Director Server Type drop-down field. You will notice that CloudLink Platform will now appear. Select CloudLink Platform.
Once CloudLink Platform is selected, the following Integrated Directory Services page will open to further define the connection type.
Enable Synchronization - Once the CloudLink-based synchronization is enabled, all existing users and new users created from the provisioning server (Azure AD) will be synced to MiCollab.
Enable Authentication
Defer all operation - Select Defer all operations to preview the synchronization updates in the detained updates queue. From the queue, you can view, apply, modify, or cancel (delete) the updates as required.
Re-initialize on next cycle - Select Re-initialize on next cycle to re-initialize the user sync from CloudLink.
This option effectively forces a full synchronization on the next scheduled sync event. A full synchronization queries the directory server for the entire set of users. This option can be used to recover the MiCollab database from the directory server. It will most likely result in a large number of detained user updates.
Note: These options can be checked or un-checked based on the requirement.
Note: The Cloudlink platform connection will available when MiCollab is integrated with Cloudlink.
MiCollab administrator can disable/enable CloudLink-based Authentication for a set of users (one or multiple) through Bulk User Provisioning (BUP). This might be required for cases where the administrator wishes to manage authentication locally through MiCollab for few users, for e.g. temporary users which don’t have accounts in AD.
For more information and steps on disabling CloudLink-based authentication, see the Admin Online Help> Applications>Users and Services> System Administrator> Bulk User provisioning section.
NOTE: All Users will now require authentication from CloudLink.
NOTE: With CloudLink Authentication including Azure AD, an email will not be sent to the users to finish building their accounts. This is because the username (email) and password are provided by Azure AD.