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:39] – lucy | ldap_integration [2019/12/19 10:32] – [Autoupdate LDAP Recipients] lucy | ||
---|---|---|---|
Line 17: | Line 17: | ||
(|(objectClass=inetOrgPerson)(objectClass=user)) | (|(objectClass=inetOrgPerson)(objectClass=user)) | ||
- | {{:ldap_settings_1.png?600|}} | + | {{:ldap_settings_7.png?600|}} |
+ | Also in the "LDAP settings" | ||
+ | |||
+ | {{: | ||
+ | |||
+ | //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. | ||
===== LDAP Update Preferences ===== | ===== LDAP Update Preferences ===== | ||
Line 63: | Line 70: | ||
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 | ||
{{ : | {{ : |
ldap_integration.txt · Last modified: 2021/11/04 18:57 by lucysecurity