LDAP Authentication is enabled when a user attempts to log on to the MiCollab Audio, Web and Video Conferencing server, a Lightweight Directory Access Protocol (LDAP) query authenticates that user. Rather than querying its own internal database to see if the username and password are authorized, an LDAP query is launched against the corporate directory. If the response indicates the username/password combination is legitimate, the server allows that user to access the system for scheduling and placing calls. Under this arrangement, the user’s password is not stored on the server, and you do not need to administer the user database on the server (except to change some enhanced service features for users).
The server also uses the LDAP query process to enable auto-provisioning. If the LDAP query indicates the username and password are legitimate but the username has not yet been identified as a user on the server, then the server automatically establishes an account for that user. The user is set up with the default level of authorization to use the system’s special features and is able to start using the system immediately. You set these user defaults when the system is initially configured (see Default User Settings).
If a user requires authorizations that differ from the system defaults, you can use the administrator Web client to change that user’s profile. See Managing a User Profile.
NOTE: To use LDAP authentication with Active Directory, you must have Active Directory set up prior to configuring MiCollab Audio, Web and Video Conferencing. Contact the site administrator to view the Active Directory configuration, and then verify the following.
- An Active Directory user exists that is used as the LDAP Admin ID. The user does not need any special rights or permissions.
- Users with name, password, and e-mail information exist as Active Directory users.
- You can ping the MiCollab Audio, Web and Video Conferencing server by hostname from the Active Directory server.
The most common LDAP authentication uses an Active Directory database. Click to view the instructions for configuring an Active Directory database.
NOTE: While applying the Microsoft security changes on the Active Directory, the sites must move from unsecure to secure LDAP. For more information, see the Manage IDS Connections topic.
NOTE:
From the MiCollab Audio, Web and Video Conferencing main page, click LDAP Configuration in the navigation pane.
Select Use LDAP if you use an LDAP server to store the user database. Otherwise, leave this option cleared and the user database is stored on the MiCollab Audio, Web and Video Conferencing server.
NOTE: When Use LDAP is set, Add User and Bulk Provision Users are not available in the MiCollab Audio, Web and Video Conferencing navigation pane.
When Use LDAP is cleared, the user database is stored on the MiCollab Audio, Web and Video Conferencing server and the settings on this page do not affect authentication.
If you select Use LDAP (in step 2), enter or edit the following LDAP server configuration options.
LDAP Server Name
LDAP Port No.
LDAP Search Base
LDAP Administrator ID
LDAP Administrator ID Password
LDAP UID Field
E-mail Domain
Auto synchronize
Sync interval (in minutes)
Click Submit, and then click Ok at the prompt.
Log on using the username (not the e-mail address) of a user listed in the Active Directory, along with their Active Directory password. The MiCollab Audio, Web and Video Conferencing server checks the Active Directory for authentication and allows the user to log on.
NOTE: The name and password are sent as plain text and present a possible security risk.
After the user has logged on, they are automatically added to a list of users that can be viewed and administered through the MiCollab Audio, Web and Video Conferencing admin Web client.