ldap_integration
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ldap_integration [2019/06/03 10:56] – lucy | ldap_integration [2020/08/25 14:43] – [LDAP Sync tool for Windows] lucy | ||
---|---|---|---|
Line 3: | Line 3: | ||
LUCY has an LDAP API, which allows the administrator to: | LUCY has an LDAP API, which allows the administrator to: | ||
- | * import recipients | + | * import recipients |
- | * import | + | * authorize |
- | directly from your directory service. | + | ==== Sync tool for Windows ==== |
+ | |||
+ | Besides LDAP API, there is a tool that can be run on Windows machines to sync your Active Directory groups with Lucy, see more [[ldap_synchronization_tool|here]]. | ||
Line 21: | Line 23: | ||
Also in the "LDAP settings" | Also in the "LDAP settings" | ||
- | {{:ldap_settings_5.png?400|}} | + | {{:ldap_settings_8.png?400|}} |
+ | |||
+ | //Note:// The Global Catalogue allows the connection only via two special ports: 3268 or 3269. To use this functionality, | ||
The global catalog (GC) allows users and applications to find objects in an Active Directory domain tree, given one or more attributes of the target object. The global catalog contains a partial replica of every naming context in the directory. It contains the schema and configuration naming contexts as well. This means the GC holds a replica of every object in the directory but with only a small number of their attributes. The attributes in the GC are those most frequently used in search operations (such as a user's first and last names or login names) and those required to locate a full replica of the object. | The global catalog (GC) allows users and applications to find objects in an Active Directory domain tree, given one or more attributes of the target object. The global catalog contains a partial replica of every naming context in the directory. It contains the schema and configuration naming contexts as well. This means the GC holds a replica of every object in the directory but with only a small number of their attributes. The attributes in the GC are those most frequently used in search operations (such as a user's first and last names or login names) and those required to locate a full replica of the object. | ||
Line 68: | Line 72: | ||
It is possible to configure LUCY autoupdate recipient list of from an LDAP Server. | It is possible to configure LUCY autoupdate recipient list of from an LDAP Server. | ||
- | Note, this configuration will not be active if there are global settings for recipients import | + | |
+ | :!: Note, this configuration will not be active if there are global settings for recipients import | ||
{{ : | {{ : | ||
Line 101: | Line 106: | ||
* 4.Phone - recipient phone number | * 4.Phone - recipient phone number | ||
+ | To configure other recipient fields to match Active Directory attributes go to the LDAP Fields Associations page (Settings > LDAP Settings > LDAP Fields Associations): | ||
+ | |||
+ | {{ :: | ||
+ | :!: Recipient' |
ldap_integration.txt · Last modified: 2021/11/04 18:57 by lucysecurity