• Type: Suggestion
• Resolution: Done
• Fix Version/s: 4.2.0, 4.0.3, 4.1.1
• Component/s: Directory - LDAP
• Labels:

  None

[CWD-5615] Do not fetch invocationId when incremental sync is disabled.

Alex [Atlassian,PSE] made changes - 06/Jun/2023 2:37 AM

Remote Link

Original: This issue links to "KRAK-3631 (Bulldog)" [ 496159 ]

New: This issue links to "KRAK-3631 (JIRA Server (Bulldog))" [ 496159 ]

Jakub Podeszwik (Inactive) made changes - 30/Nov/2020 10:06 AM

Link

New: This issue is related to CWD-5572 [ CWD-5572 ]

Rob made changes - 31/Aug/2020 2:22 AM

Remote Link

New: This issue links to "Page (Confluence)" [ 501785 ]

Dawid Owoc (Inactive) made changes - 12/Aug/2020 3:15 PM

Remote Link

New: This issue links to "Page (Confluence)" [ 499205 ]

Dawid Owoc (Inactive) made changes - 12/Aug/2020 2:20 PM

Fix Version/s

New: 4.2.0 [ 92192 ]

Jakub Podeszwik (Inactive) made changes - 24/Jul/2020 2:50 PM

Description

Original: h3. Issue Summary When using AD Connector, Crowd will try to fetch invocationId, and highestCommitedUSN at the end of synchronisation process. It will happen even if incremental synchronisation is disabled. Those values are not needed for full synchronisation.   Some of the customers that are using AD LDS (not supported) are experiencing failures in synchronisation process when using AD Connector. This is caused by differences between AD and AD LDS. After this change is implemented, workaround for such issues is to disable incremental sync.

New: h3. Issue Summary When using AD Connector, Crowd will try to fetch invocationId, and highestCommitedUSN at the end of synchronisation process. It will happen even if incremental synchronisation is disabled. Those values are not needed for full synchronisation.   Some of the customers that are using AD LDS (not supported) are experiencing failures related to fetching invocationId in synchronisation process when using AD Connector. This is caused by differences between AD and AD LDS. After this change is implemented, workaround for such issues is to disable incremental sync.

Jakub Podeszwik (Inactive) made changes - 24/Jul/2020 2:47 PM

Description

Original: h3. Issue Summary When using AD Connector, Crowd will try to fetch invocationId, and highestCommitedUSN at the end of synchronisation process. It will happen even if incremental synchronisation is disabled. Those values are not needed for full synchronisation.   Some of the customers that are using AD LDS (not supported) are experiencing failures in synchronisation process when using AD Connector. This is caused by differences between AD and AD LDS. After this change is implemented workaround for such issues is to disable incremental sync.

New: h3. Issue Summary When using AD Connector, Crowd will try to fetch invocationId, and highestCommitedUSN at the end of synchronisation process. It will happen even if incremental synchronisation is disabled. Those values are not needed for full synchronisation.   Some of the customers that are using AD LDS (not supported) are experiencing failures in synchronisation process when using AD Connector. This is caused by differences between AD and AD LDS. After this change is implemented, workaround for such issues is to disable incremental sync.

Jakub Podeszwik (Inactive) made changes - 24/Jul/2020 2:46 PM

Description

Original: h3. Issue Summary When using AD Connector, Crowd will try to fetch invocationId, and highestCommitedUSN at the end of synchronisation process. It will be happen even if incremental synchronisation is disabled. Those values are not needed for full synchronisation.   Some of the customers that are using AD LDS (not supported) are experiencing failures in synchronisation process when using AD Connector. This is caused by differences between AD and AD LDS. After this change is implemented workaround for such issues is to disable incremental sync.

New: h3. Issue Summary When using AD Connector, Crowd will try to fetch invocationId, and highestCommitedUSN at the end of synchronisation process. It will happen even if incremental synchronisation is disabled. Those values are not needed for full synchronisation.   Some of the customers that are using AD LDS (not supported) are experiencing failures in synchronisation process when using AD Connector. This is caused by differences between AD and AD LDS. After this change is implemented workaround for such issues is to disable incremental sync.

Jakub Podeszwik (Inactive) made changes - 24/Jul/2020 2:46 PM

Remote Link

New: This issue links to "KRAK-3631 (Bulldog)" [ 496159 ]

Jakub Podeszwik (Inactive) made changes - 24/Jul/2020 2:45 PM

Description

Original: h3. Issue Summary When using AD Connector Crowd will try to fetch invocationId, and highestCommitedUSN at the end of synchronisation process. It will be happen even if incremental synchronisation is disabled. Those values are not needed for full synchronisation.   Some of the customers that are using AD LDS (not supported) are experiencing failures in synchronisation process when using AD Connector. This is caused by differences between AD and AD LDS. After this change is implemented workaround for such issues is to disable incremental sync.

New: h3. Issue Summary When using AD Connector, Crowd will try to fetch invocationId, and highestCommitedUSN at the end of synchronisation process. It will be happen even if incremental synchronisation is disabled. Those values are not needed for full synchronisation.   Some of the customers that are using AD LDS (not supported) are experiencing failures in synchronisation process when using AD Connector. This is caused by differences between AD and AD LDS. After this change is implemented workaround for such issues is to disable incremental sync.

Load more older events