McDewey

C H A P T E R 12 LDAP • Overview, on page 147 • Integrating Unity Connection with an LDAP Directory, on page 147 • Task List for Configuring LDAP, on page 148 • Editing LDAP Directory Configuration, on page 157 • Changing LDAP Integration Status, on page 159 Overview When you are using an LDAP compliant directory as your corporate directory and do not want to separately maintain basic user information in Cisco Unity Connection, you can use the LDAP integration feature. The LDAP integration in Unity Connection involves: • Creating Unity Connection users by importing user data from an LDAP directory. • Configuring Unity Connection to periodically synchronize the users with the user data in an LDAP directory. • Authenticating Unity Connection users against the user data in an LDAP directory. An LDAP authenticated user uses the LDAP password as the web application password to log in to Unity Connection web applications. For a list of the LDAP directories that are supported for use with Unity Connection, see the “Requirements for an LDAP Directory Integration” section in System Requirements for Cisco Unity Connection Release 15 available at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/15/requirements/b_ 15cucsysreqs.html. Integrating Unity Connection with an LDAP Directory If a Unity Connection server is integrated with a Cisco Unified CM phone system and you want to integrate both the servers with an LDAP directory, you must separately integrate each server with the LDAP directory. Integrating only one of the servers with an LDAP directory is not sufficient to allow the other server to synchronize or authenticate to the LDAP directory. See the related links: System Administration Guide 147