-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Currently, while using AD LDS with the AD Connector in Atlassian Crowd versions v3.6.0 and above, syncing will fail when Crowd attempts to fetch the AD server InvocationId. This is due to AD LDS presenting a different schema than what the AD Connector is expecting.
The current workaround is to use either use Atlassian Crowd v3.5.1 (or prior) or use the generic connector to complete the sync (however this doesn't support incremental sync like with the AD Connector).
Official request to support AD LDS in the AD Connector for future versions beyond 3.5.1