MACROMEDIA BREEZE-USING THE MACROMEDIA BREEZE MANAGER Manuale Utente

Best Practices for Breeze Directory Service Integration

10 Best Practice for Breeze Directory Service IntegrationThere are two ways of relating group and user entries in LDAP directories. A directory may be

Working with LDAP 11Importing sub-branchesLet us suppose that you have set the Branch DN on the User Profile Mapping screen to import all the users in

12 Best Practice for Breeze Directory Service IntegrationWorking with branches in Directory ServiceWhen importing users and groups from an LDAP-compli

Working with LDAP 13The User Branch editor, shown below, is used to select the users for import. The Marketing node from the above example is selected

14 Best Practice for Breeze Directory Service IntegrationManaging passwordsWhen Breeze imports user information using DSI, this does not provide Breez

Managing passwords 15If you plan on using either of these methods for single sign-on authentication, you will want set the authentication policy for D

16 Best Practice for Breeze Directory Service IntegrationTo set Breeze configuration variables manually for authentication integration:1. Stop all Bre

Managing passwords 17HTTP header-based authenticationHTTP header-based authentication uses extra fields in the header of an HTTP request for authentic

18 Best Practice for Breeze Directory Service IntegrationSetting the password to an LDAP attributeUnder this scenario, DSI would set the initial passw

Recommended practices for synchronization 19If you anticipate relatively few changes of LDAP server entries between scheduled synchronizations, you ma

Trademarks1 Step RoboPDF, ActiveEdit, ActiveTest, Authorware, Blue Sky Software, Blue Sky, Breeze, Breezo, Captivate, Central, ColdFusion, Contribute,

20 Best Practice for Breeze Directory Service IntegrationLog file formatThe synchronization logs store values in a comma-separated format. In the tabl

Recommended practices for synchronization 21Previewing the synchronizationBefore you try to import users and groups in an initial synchronization, it

22 Best Practice for Breeze Directory Service IntegrationLogs consist of events with one line per event. The synchronization produces at least one eve

Questions about Breeze Directory Service Integration 23 What if there is a make a mistake when importing thousands of users and I want to start over

24 Best Practice for Breeze Directory Service Integration

3ContentsBest Practice for Breeze Directory Service Integration . . . . . . . . . 5Working with LDAP. . . . . . . . . . . . . . . . . . . . . . . . .

4Contents

5Best Practice for Breeze Directory Service IntegrationWorking with LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 Best Practice for Breeze Directory Service IntegrationTo perform a directory integration task, you must be defined as an administrator in your Breez

Working with LDAP 7The required fields are: Login, First Name, Last Name, and Email. If you have defined any custom fields (Breeze Administration >

8 Best Practice for Breeze Directory Service IntegrationImporting groupsTo map LDAP group entry attributes to Breeze group profiles, the administrator

Working with LDAP 9Selecting the directory node to be importedWhen importing users and groups from an LDAP directory into Breeze, you specify a path t