Open issues

Order by Priority
  1. Suggestion
    CWD-5707As an admin I would like a full sync to be triggered when "nested groups" is enabled
  2. Suggestion
    CWD-5675Introduce SCIM 2.0 support in Crowd DC
  3. Suggestion
    CWD-6351Upgrade bundled Tomcat to 9.0.99 or higher
  4. Suggestion
    CWD-5673Allow Crowd to disable requests that phone home
  5. Suggestion
    CWD-1822General SAML Support
  6. Suggestion
    CWD-6352Generating a list of Crowd users added to groups on or after a specific date is not possible using the Crowd REST APIs
  7. Suggestion
    CWD-6347Reintroduce Microsofts LDAP Matching rules for Crowd
  8. Suggestion
    CWD-6350Add an option to Microsoft Entra ID directory type available for other directory types
  9. Suggestion
    CWD-1930Add UI to bulk Activate/Deactivate users
  10. Suggestion
    CWD-1029Show clearer error in atlassian-crowd.log file if login fails due to domain property that does not match the application's domain.
  11. Suggestion
    CWD-4984A form of notification should user directories failed to synchronize
  12. Suggestion
    CWD-5531Improve Crowd REST API description for admin/1.0/groups
  13. Suggestion
    CWD-5738Improve Crowd DC installation doc
  14. Suggestion
    CWD-5958Create crowd.cfg.xml file while deploying Crowd on docker or K8s environment
  15. Suggestion
    CWD-6286Provide an option to modify Crowd Schedule Jobs
  16. Suggestion
    CWD-6311Group administration with delegated directories
  17. Suggestion
    CWD-1636Support PAPE for OpenID Anti-Phishing Security
  18. Suggestion
    CWD-2759Force application sync on add user event
  19. Suggestion
    CWD-3822Crowd does not create indexes for cwd_application_alias
  20. Suggestion
    CWD-5552Ability to Filter users and groups For AzureAD in Crowd standalone version
  21. Suggestion
    CWD-5567As a group administrator, I'd like to manage groups within the group I administer
  22. Suggestion
    CWD-5600Allow ability to add groups to the Azure AD group filter in bulk
  23. Suggestion
    CWD-5693Allow Administrators to Configure the Content Security Policy
  24. Suggestion
    CWD-5765Option to keep LDAP users and groups inside the cwd_user and cwd_group table although the users or groups could not be found during the directory synchronisation.
  25. Suggestion
    CWD-6277Troubleshooting would be easier with StuckThreadDetectionValve set by default
  26. Suggestion
    CWD-3908Update screenshots in Crowd's documentation
  27. Suggestion
    CWD-4969CSV Importer: Import Group Membership File without User File
  28. Suggestion
    CWD-5159Provide Read-Only Access to Crowd Admins
  29. Suggestion
    CWD-5261Create Crowd Data Center deployment app in Azure marketplace
  30. Suggestion
    CWD-5666Provide an option to create/download Support from all the nodes in Crowd DC
  31. Suggestion
    CWD-5679API that creates a group in a specific directory in Crowd
  32. Suggestion
    CWD-5739Allow configuration for LDAP connectors to retain users in Crowd when they are deleted in LDAP
  33. Suggestion
    CWD-5891Introduce a new $resetlink variable that will generate the link to reset password via the CrowdID
  34. Suggestion
    CWD-5915Crowd Data Center to support Geo-Clustering
  35. Suggestion
    CWD-6292Enable Incremental Sync for PAM changes in AD
  36. Suggestion
    CWD-598Allow authentication by PKI infrastructure
  37. Suggestion
    CWD-1681Support Windows Authentication For MS SQL Database
  38. Suggestion
    CWD-4353Application audit log for user login attempts
  39. Suggestion
    CWD-4390Restrict Admin Access to a Specific Application
  40. Suggestion
    CWD-4435Provide a supported method for unattended installations
  41. Suggestion
    CWD-4680When creating a group, require at least one member of the group that is not null if the directory type requires it
  42. Suggestion
    CWD-4963When using a read only Crowd/JIRA Directory, users attempting to change their password get an unhelpful error message
  43. Suggestion
    CWD-5397Crowd REST API to retrieve License and user count Details
  44. Suggestion
    CWD-5569Provide a way to stop synchronisation job for the directory.
  45. Suggestion
    CWD-5601Please add the ability to use dynamic lookups instead of DNS name lookups to connect to Active Directory on Crowd / Embedded Crowd
  46. Suggestion
    CWD-5618Provide support for MySQL Databases using utf8mb4
  47. Suggestion
    CWD-5643Add "Default group memberships" for Azure Active Directory
  48. Suggestion
    CWD-5703Add the ability to hide "Forgot your password?" link in the login page.
  49. Suggestion
    CWD-5907Crowd Data Center Support For Oracle Exadata HA
  50. Suggestion
    CWD-678Allow Crowd admin ability to adjust number of users if license is accidentally exceeded during configuration.
Refresh results
1 of 795
Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-5707

As an admin I would like a full sync to be triggered when "nested groups" is enabled

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Directory - LDAP
    • None
    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      When nested groups is enabled, the expected functionality is not observed until a full ldap sync is performed

      Suggested Solution

      • changing the settings to "nested groups (yes)" should somehow enforce a full sync with crowd.
      • Temporarily deactivate incremental sync after changing those settings so a full sync kicks in

      Workaround

      • manual full sync is required

            There are no comments yet on this issue.

              Unassigned Unassigned
              nhansberry Nate Hansberry
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: