WARNING: Syncing information that is not available (or NULL) from one service to the other (either from LDAP to Axigen or vice versa) can lead to the destruction of already existing information in the destination system. Special care must be advised while performing such operations as they may lead to irreparable loss of data.
The Axigen server, being configured to perform automatic syncs with an LDAP server, performs periodical queries in the directory database to detect changes. Whenever a change of a relevant LDAP entry is received, a specific event, that triggers a sync action, is generated. A relevant LDAP entry has to match either the account filter or the group filter (depending on what is being synced), in the appropriate LDAP “BaseDN” property for that entry.
The following LDAP service configuration options (in the case of accounts and, respectively, groups) are used when inquiring the LDAP server for changes:
- The LDAP BaseDN setting. This setting refers to the top of the directory tree that is used in the sync process.
- The entry Object Class type. The class refers to the type of object listed in the database. This affects the other sync options that are specific to each object type.
- Additional Filters. This value specifies the filters that apply to each entry. It is dependent on the object class type above.
- The LDAP Polling Interval. LDAP searches (that detect changes) are performed periodically, based on the settings configured in the LDAP connector (the LDAP polling interval value).
When changes between the two databases are detected, they are queued up for syncing; after no more changes are detected for the entries in the LDAP database, the Axigen service will wait for the "LDAP Polling Interval" seconds before looking up changes in the database again. This process is repeated over and over and ensures that the consistency between the two databases is achieved regularly.