MACROMEDIA BREEZE-CLUSTERING BREEZE LIVE Manuel d'utilisateur télécharger pdf (Page 30)

ADOBE CONNECT ENTERPRISE SERVER 6

Installation and Configuration Guide

To integrate with Connect Enterprise, your directory server must use Lightweight Directory Access Protocol (LDAP)

or secure Lightweight Directory Access Protocol (LDAPS). LDAP is an Internet client-server protocol for lookup of

user contact information from an LDAP-compliant directory server.

Connect Enterprise connects as an LDAP client to an LDAP directory, imports users and groups, and ensures that

information about these users and groups in the database is kept synchronized with the external LDAP directory.

Adobe has tested directory service integration with the following LDAP servers:

• Active Directory Application Mode (ADAM) SP1

• Active Directory (Windows Server 2003 and Windows Server 2000)

• IBM Directory Server 5.2

• Novell eDirectory 8.7.3 for Win32

• OpenLDAP 2.3.19

• Sun One Directory Server 5.2 for Win32

• Netscape 6.02 for Win32

There are several important concepts to understand before configuring and performing a directory service

integration. These concepts are explained in the following sections. If you have experience with LDAP directory

structure and LDAP integration, you may want to go directly to “Integrating Connect Enterprise with an LDAP

directory” on page 28.

About LDAP directory structure

LDAP directories organize information according to the X.500 standard.

A user or group in an LDAP directory is called an entry. An entry is a collection of attributes. An attribute consists

ofatypeandoneormorevalues.Typesusemnemonicstrings,suchas

ou for organizational unit or cn for common

name. Attribute values consist of information such as phone number, e-mail address, and photo. To determine your

organization’s LDAP directory structure, contact your LDAP administrator.

Each entry has a distinguished name (DN) that describes a path to the entry through a tree structure from the entry

to the root. The DN for an entry in the LDAP directory is a concatenation of the name of the entry (called a relative

distinguished name, RDN) and the names of its ancestor entries in the tree structure.

A tree structure may reflect geographical locations or departmental boundaries within a company. For example, if

Alicia Solis is a user in the QA department of Acme, Inc. in France, the DN for this user might be as follows:

cn=Alicia Solis, ou=QA, c=France, dc=Acme, dc=com

Importing directory branches

When importing users and groups from an LDAP directory into Connect Enterprise, you specify a path to a section

oftheLDAPtreebyusingtheDNofthesection.Thisspecifiesthescopeofthesearch.Forexample,youmaywant

to import only the users of a particular group within your organization. To do this, you need to know where the

entries for that group are located in the directory tree structure.

A common technique is to use the organization’s Internet domain as the root for the tree structure. For example,

Acme,Inc.mightuse

dc=com to specify the root element in the tree. A DN that specifies the Singapore sales office for

Acme, Inc. might be

ou=Singapore, ou=Marketing, ou=Employees, dc=Acme, dc=com. (In this example, ou is an abbrevi-

ation for organizational unit, and

dc is an abbreviation for domain component.)

Note: Not all LDAP directories have a single root. In this situation, you can import separate branches.

1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 61 62

Commentaires sur ces manuels

Pas de commentaire

MACROMEDIA BREEZE-CLUSTERING BREEZE LIVE Manuel d'utilisateur Page 30

Commentaires sur ces manuels