-
Bug
-
Resolution: Fixed
-
Low
-
3.0.1, 3.0.2, 3.2.1
-
Severity 1 - Critical
-
Summary
After adding the Azure connector or doing a full synchronization all membership to the groups will not be synchronized to the Crowd from Azure AD.
Environment
- Azure AD
- Latest Crowd (tested with 3.2.1)
How to Replicate
- Set AZURE AD directory on Crowd
- After synchronization,
Expected Results
- users, groups, and membership to the groups to be synched normally on Crowd
Actual results
- Users and groups synched, but users are not showing under their respective groups on Crowd.
Notes and Resolution
The issue has been fixed in Crowd 3.0.3, 3.1.4 and 3.2.2 - please update to any of these versions to obtain the fix.
It may however occur that Crowd continues to incrementally synchronize with Azure AD, without picking up the existing memberships. In such case it's possible to force a full synchronization using the following steps:
- Uncheck the "Enable incremental sync" checkbox
- Click the "Update" button
- Check the "Enable incremental sync" checkbox
- Click the "Update" button again
[CWD-5192] Azure AD synchronisation remove membership
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 2694946 ] | New: JAC Bug Workflow v3 [ 3366072 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Component/s | New: Directory - Azure Active Directory [ 58192 ] |
| Symptom Severity | Original: Critical [ 14430 ] | New: Severity 1 - Critical [ 15830 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 389070 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 375901 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 375085 ] |
| Description |
Original:
h3. Fix and update notes
The issue has been fixed in Crowd 3.0.3, 3.1.4 and 3.2.2. It may however occur that Crowd continues to incrementally synchronize with Azure AD, without picking up the existing memberships. In such case it's possible to force a full synchronization using the following steps: * Uncheck the "Enable incremental sync" checkbox * Click the "Update" button * Check the "Enable incremental sync" checkbox * Click the "Update" button again h3. Summary After adding the Azure connector or doing a full synchronization all membership to the groups will not be synchronized to the Crowd from Azure AD. h3. Environment * Azure AD * Latest Crowd (tested with 3.2.1) h3. How to Replicate # Set AZURE AD directory on Crowd # After synchronization, h3. Expected Results * users, groups, and membership to the groups to be synched normally on Crowd h3. Actual results * Users and groups synched, but users are not showing under their respective groups on Crowd. h3. Workaround No known workaround at the moment. h3. Notes It looks like Microsoft API for Azure AD has changed. At the moment there is no documentation about it. |
New:
h3. Summary
After adding the Azure connector or doing a full synchronization all membership to the groups will not be synchronized to the Crowd from Azure AD. h3. Environment * Azure AD * Latest Crowd (tested with 3.2.1) h3. How to Replicate # Set AZURE AD directory on Crowd # After synchronization, h3. Expected Results * users, groups, and membership to the groups to be synched normally on Crowd h3. Actual results * Users and groups synched, but users are not showing under their respective groups on Crowd. h3. Notes and Resolution The issue has been fixed in Crowd 3.0.3, 3.1.4 and 3.2.2 - please update to any of these versions to obtain the fix. It may however occur that Crowd continues to incrementally synchronize with Azure AD, without picking up the existing memberships. In such case it's possible to force a full synchronization using the following steps: * Uncheck the "Enable incremental sync" checkbox * Click the "Update" button * Check the "Enable incremental sync" checkbox * Click the "Update" button again |
| Description |
Original:
h3. Summary
After adding the Azure connector or doing a full synchronization all membership to the groups will not be synchronized to the Crowd from Azure AD. h3. Environment * Azure AD * Latest Crowd (tested with 3.2.1) h3. How to Replicate # Set AZURE AD directory on Crowd # After synchronization, h3. Expected Results * users, groups, and membership to the groups to be synched normally on Crowd h3. Actual results * Users and groups synched, but users are not showing under their respective groups on Crowd. h3. Workaround No known workaround at the moment. h3. Notes It looks like Microsoft API for Azure AD has changed. At the moment there is no documentation about it. |
New:
h3. Fix and update notes
The issue has been fixed in Crowd 3.0.3, 3.1.4 and 3.2.2. It may however occur that Crowd continues to incrementally synchronize with Azure AD, without picking up the existing memberships. In such case it's possible to force a full synchronization using the following steps: * Uncheck the "Enable incremental sync" checkbox * Click the "Update" button * Check the "Enable incremental sync" checkbox * Click the "Update" button again h3. Summary After adding the Azure connector or doing a full synchronization all membership to the groups will not be synchronized to the Crowd from Azure AD. h3. Environment * Azure AD * Latest Crowd (tested with 3.2.1) h3. How to Replicate # Set AZURE AD directory on Crowd # After synchronization, h3. Expected Results * users, groups, and membership to the groups to be synched normally on Crowd h3. Actual results * Users and groups synched, but users are not showing under their respective groups on Crowd. h3. Workaround No known workaround at the moment. h3. Notes It looks like Microsoft API for Azure AD has changed. At the moment there is no documentation about it. |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Hello,
The fix is available in Crowd 3.0.3, Crowd 3.1.4 and Crowd 3.2.2. It may however occur that Crowd continues to incrementally synchronize with Azure AD, not picking up the existing memberships. In such case please:
Best regards,
Patryk Petrowski