The AD Sync solution consists of 3 different components, where each component is split in another parts.
The AD Change Workers are the ones that pull changes from an active directory. One worker is responsible for incoming changes, one worker for incoming delete changes and the last is responsible for the password synchronisation.
| Parameter | Description | Default value |
|---|---|---|
| User | Ldap Server Name or IP | "127.0.0.1" |
| Password | LDAP Port to be used | 389 |
| BaseDN | Use TLS for LDAP Connections | false |
| Listen | Fallback to simple / single ops if the given Fails ? | false |
| Class | Fallback to simple / single ops if the given Fails ? | false |
| Operation | Fallback to simple / single ops if the given Fails ? | false |
| Filter | Fallback to simple / single ops if the given Fails ? | false |
| FetchAttr | Fallback to simple / single ops if the given Fails ? | false |
Make sure you use the value change as Listen parameter and uSNChanged,objectClass as FetchAttr parameter. The Class and Operation parameters have to point to the AD Dispatcher Workflow’s InputChan (e.g. Class=object, Operation=dispatch, InputChan=object_dispatch).
The last serial number the worker processed will be stored in a file called /data/serial.dat. If you are using Docker mount the whole folder into your volume.
Make sure you use the value delete as Listen parameter and uSNChanged,objectClass as FetchAttr parameter. The Class and Operation parameters have to point to the AD Dispatcher Workflow’s InputChan (e.g. Class=object, Operation=dispatch, InputChan=object_dispatch). As well the BaseDN parameter has to be pointed to the Deleted Objects Object e.g. CN=Deleted Objects,DC=example,DC=com.
The same applies to the delete, only the file is called /data/serial.del.dat.
Make sure you use the value password as Listen parameter. The Class and Operation parameters have to point to the Password Sync Workflow’s InputChan (e.g. Class=password, Operation=change, InputChan=password_change).
text
text
bla bla
text
text
Text