The Active Directory integration involves the use of the Axigen extension provided, to allow extending the standard AD schema with the required Axigen attributes, as well as a Management Console (MMC) property page, to allow graphical editing of Axigen specific attributes when an account is modified to include the aforementioned properties.

The Axigen server, being configured to perform automatic syncs with an Active Directory service, performs periodical queries in the directory database to detect changes. Whenever a change of a relevant Active Directory entry is received, a specific event, that triggers a sync action, is generated. A relevant Active Directory entry has to match either the account filter or the group filter (depending on what is being synced), in the appropriate Active Directory “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).

Active Directory searches (that detect changes) are performed periodically, based on the parameter configured in the LDAP connector (LDAP polling interval). If changes are detected, they are queued; after no more changes exist in LDAP, the thread sleeps for "LDAP Polling Interval" seconds, then a new search is performed.