-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
19
-
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
[CWD-5572] Support AD LDS using the AD Connector in future versions of Crowd
Support reference count | Original: 18 | New: 19 |
Support reference count | Original: 17 | New: 18 |
Support reference count | New: 17 |
Remote Link | Original: This issue links to "PS-57428 (Atlassian Support System)" [ 480209 ] |
Remote Link | New: This issue links to "PS-57428 (Atlassian Support System)" [ 480209 ] |
Description |
Original:
Currently, while using AD LDS with the AD Connector in Atlassin 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 |
New:
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 |
Description |
Original:
Currently, while using AD LDS with the AD Connector in Atlassin 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. |
New:
Currently, while using AD LDS with the AD Connector in Atlassin 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 |
Description |
Original:
Currently, while using AD LDS with the AD Connector in Atlassin Crowd versions 3.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. |
New:
Currently, while using AD LDS with the AD Connector in Atlassin 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. |