Cisco Cisco MeetingTime Quick Setup Guide

Page of 766
Configuring User Authentication for Cisco Unified MeetingPlace Web Conferencing
How to Configure LDAP then MeetingPlace Authentication
7
 
Verifying the LDAP Authentication Configuration by Using the HTTP Form
Use a Cisco Unified MeetingPlace end-user profile when completing this procedure.
Before You Begin
Complete the 
.
Procedure
Step 1
Open a web browser and navigate to Cisco Unified MeetingPlace.
Step 2
Verify the following end-user behaviors:
  •
When you access the Cisco Unified MeetingPlace home page, you see an Enter Network Password 
window.
  •
After you enter your LDAP profile user ID and password, you are authenticated to the Cisco Unified 
MeetingPlace Application Server.
  •
The Welcome page displays your name in firstname, lastname order.
  •
Sign In and Sign Out links do not display.
Related Topics
  •
How to Configure LDAP then MeetingPlace Authentication
This authentication mode attempts to authenticate users against two directories if the need arises. When 
users first log in, they are authenticated against the LDAP directory. If this authentication fails, the login 
information is sent to the Cisco Unified MeetingPlace Application Server for a possible match. This 
behavior allows a company to give non-LDAP users, such as guests or contractors, access to 
Cisco Unified MeetingPlace.
Note
Cisco Unified MeetingPlace enforces e-mail format validation when you have LDAP synchronization 
configured. If an e-mail address for a particular user does not conform to the standard e-mail format, the 
user is skipped during the LDAP synchronization process and not imported into the MeetingPlace 
database. Standard email addresses are in the form user@domain. User is limited to upper and lower case 
alphanumeric characters and period (dot), dash, and underscore. Domain is limited to alphanumeric 
characters and period (dot) and dash (no underscore). No spaces are permitted.
  •
  •
  •
  •