Univention Bugzilla – Bug 41685
AD Connector: Extend syncmode options
Last modified: 2016-09-28 14:40:57 CEST
The S4 connector can have a different "syncmode" (write, read, sync) for every object type it can sync. This means I could do sth. like this:
The AD connector is much more limited in this case, as it checks only two variables, a global one and one especially for computer objects:
We should extend the feature set of the AD connector to the feature set of the S4 Connector. The code exists in the AD connector mapping, but it always checks "connector/ad/mapping/syncmode" for each and every object type (except computer objects), instead of an object type specific UCRV.
UCS 4.1-3: r72533
UCS 4.2: r72534
The following UCR variables have been added:
Not yet tested.
(In reply to Stefan Gohmann from comment #1)
> UCS 4.1-3: r72533
> UCS 4.2: r72534
> YAML: r72535
> The following UCR variables have been added:
> - connector/ad/mapping/user/syncmode
> - connector/ad/mapping/group/syncmode
> - connector/ad/mapping/container/syncmode
> - connector/ad/mapping/ou/syncmode
> Not yet tested.
My tests were successful.
syncmode sync, read, write, none tested with
* ou (connector/ad/mapping/ou/syncmode) - OK
* container (connector/ad/mapping/container/syncmode) - OK
* group (connector/ad/mapping/group/syncmode) - OK
* users (connector/ad/mapping/user/syncmode) - OK
OK - merged to 4.2-0
OK - yaml
*** Bug 42525 has been marked as a duplicate of this bug. ***