Cisco Cisco MeetingTime Quick Setup Guide

When you access the Cisco Unified MeetingPlace home page, you see an Enter Network Password 
window.

After you enter your end-user Cisco Unified MeetingPlace 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.

LDAP authentication compares user login information against the profile database on an 
LDAPv2-compliant directory server. After users are authenticated by the LDAP server, they are 
automatically logged in to Cisco Unified MeetingPlace as long as their LDAP user IDs also exist in 
Cisco Unified MeetingPlace. You can also authenticate users against a multiple LDAP forest 
configuration.

With LDAP authentication, the following restrictions apply:

Cisco Unified MeetingPlace Web Conferencing supports only unencrypted LDAP, that is, queries 
to the LDAP server are in clear text.

Users cannot log in with their Cisco Unified MeetingPlace passwords for their same LDAP user 
names.

LDAP profiles are used for authentication; Cisco Unified MeetingPlace profile passwords are 
ignored.

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 e-mail format expressions include: 
^([\\w-_.'])*\\w+@([\\da-zA-Z-]+\\.)+[\\da-zA-Z]{2,6}$

To authenticate the web conferencing application 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).

Read the