Cisco Cisco Unified MeetingPlace Audio Server Quick Setup Guide
Configuring User Authentication for Cisco Unified MeetingPlace Web Conferencing
How to Configure LDAP then MeetingPlace Authentication
8
Prerequisites for Configuring LDAP Then MeetingPlace Authentication
•
To authenticate Cisco Unified MeetingPlace Web Conferencing against the LDAP server, make
sure that the LDAP server directory is designed to have all users in one container rather than broken
into multiple containers (each representing a child OU).
sure that the LDAP server directory is designed to have all users in one container rather than broken
into multiple containers (each representing a child OU).
•
If a match is made in the LDAP database, the user must provide the proper LDAP password. Three
attempts with the incorrect password will lock the LDAP profile of the user.
attempts with the incorrect password will lock the LDAP profile of the user.
•
Only users who are not found in the LDAP directory are eligible for authentication through the
Cisco Unified MeetingPlace directory.
Cisco Unified MeetingPlace directory.
•
User IDs in the Cisco Unified MeetingPlace profile database are not case-sensitive.
Related Topics
•
Configuring the LDAP Then MeetingPlace Authentication
Before You Begin
Read the
Procedure
Step 1
Sign in to the end-user web interface.
Step 2
Select Admin.
Step 3
Select Web Server.
Step 4
Select the name of the Web Server that you want to configure in the “View” section of the page.
Step 5
Scroll to the Web Authentication section.
Step 6
Select LDAP, then MeetingPlace for “Step 1: Directory”.
Step 7
Enter the LDAP hostname in the field provided.
Example: ldap.domain.com
Step 8
Enter the Distinguished Name (DN) information for your directory in the field provided noting the
following considerations:
following considerations:
•
Cisco Unified MeetingPlace user profile login names are limited to 17 characters; therefore, the
LDAP match must be 17 characters or less.
LDAP match must be 17 characters or less.
•
You can only enter one value for the LDAP Distinguished Name (DN) field. If your users are
segregated into multiple organizational units (OUs), you can work around this issue by using either
the DOMAIN\USER or user@ou.domain.com format for the DN. When configuring the LDAP
Distinguished Name field, enter just %USERNAME%, without specifying an OU, DC, orother
parameter.
segregated into multiple organizational units (OUs), you can work around this issue by using either
the DOMAIN\USER or user@ou.domain.com format for the DN. When configuring the LDAP
Distinguished Name field, enter just %USERNAME%, without specifying an OU, DC, orother
parameter.
–
You are authenticating against a multiple LDAP forest configuration. Example:
CN=%USERNAME%, OU=People, DC=mydomain, DC=com.
CN=%USERNAME%, OU=People, DC=mydomain, DC=com.
–
The LDAP server you are using is the LDAP interface on a Microsoft ActiveDirectory server.
If this is the case, you must leave the DN field blank forauthentication to work. When
configured in this manner, the format of the user names that the user enters must be
DOMAIN\USER oruser@ou.domain.com.
If this is the case, you must leave the DN field blank forauthentication to work. When
configured in this manner, the format of the user names that the user enters must be
DOMAIN\USER oruser@ou.domain.com.