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-3717Allow incremental sync when a remote Crowd delegated authentication directory is used
  4. Suggestion
    CWD-6351Upgrade bundled Tomcat to 9.0.99 or higher
  5. Suggestion
    CWD-5673Allow Crowd to disable requests that phone home
  6. Suggestion
    CWD-1822General SAML Support
  7. 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
  8. Suggestion
    CWD-1599Ability to rename groups
  9. Suggestion
    CWD-6347Reintroduce Microsofts LDAP Matching rules for Crowd
  10. Suggestion
    CWD-6350Add an option to Microsoft Entra ID directory type available for other directory types
  11. Suggestion
    CWD-1930Add UI to bulk Activate/Deactivate users
  12. Suggestion
    CWD-5322add support for Azure Multi-factor authentication
  13. Suggestion
    CWD-5531Improve Crowd REST API description for admin/1.0/groups
  14. Suggestion
    CWD-5738Improve Crowd DC installation doc
  15. Suggestion
    CWD-5958Create crowd.cfg.xml file while deploying Crowd on docker or K8s environment
  16. Suggestion
    CWD-6311Group administration with delegated directories
  17. Suggestion
    CWD-3822Crowd does not create indexes for cwd_application_alias
  18. Suggestion
    CWD-5552Ability to Filter users and groups For AzureAD in Crowd standalone version
  19. Suggestion
    CWD-5567As a group administrator, I'd like to manage groups within the group I administer
  20. Suggestion
    CWD-5600Allow ability to add groups to the Azure AD group filter in bulk
  21. Suggestion
    CWD-5693Allow Administrators to Configure the Content Security Policy
  22. 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.
  23. Suggestion
    CWD-6277Troubleshooting would be easier with StuckThreadDetectionValve set by default
  24. Suggestion
    CWD-5666Provide an option to create/download Support from all the nodes in Crowd DC
  25. Suggestion
    CWD-5679API that creates a group in a specific directory in Crowd
  26. Suggestion
    CWD-5739Allow configuration for LDAP connectors to retain users in Crowd when they are deleted in LDAP
  27. Suggestion
    CWD-5891Introduce a new $resetlink variable that will generate the link to reset password via the CrowdID
  28. Suggestion
    CWD-5915Crowd Data Center to support Geo-Clustering
  29. Suggestion
    CWD-4963When using a read only Crowd/JIRA Directory, users attempting to change their password get an unhelpful error message
  30. Suggestion
    CWD-5569Provide a way to stop synchronisation job for the directory.
  31. Suggestion
    CWD-5601Please add the ability to use dynamic lookups instead of DNS name lookups to connect to Active Directory on Crowd / Embedded Crowd
  32. Suggestion
    CWD-5618Provide support for MySQL Databases using utf8mb4
  33. Suggestion
    CWD-5643Add "Default group memberships" for Azure Active Directory
  34. Suggestion
    CWD-5703Add the ability to hide "Forgot your password?" link in the login page.
  35. Suggestion
    CWD-5907Crowd Data Center Support For Oracle Exadata HA
  36. Suggestion
    CWD-5529Enable JMX remote monitoring in Crowd Server
  37. Suggestion
    CWD-5769Sync group deletion when using delegated user directory
  38. Suggestion
    CWD-5786Required REST API or Curl Command to bulk update all the existing Crowd user group with newly added Group Admin user/group of users.
  39. Suggestion
    CWD-6346Disable "Can't log in?" link [SO292775]
  40. Suggestion
    CWD-5697HTTP Options
  41. Suggestion
    CWD-5728Crowd with Oracle multitenant mode support
  42. Suggestion
    CWD-5751Update Centralised license visibility for Jira & Bitbucket
  43. Suggestion
    CWD-6336Ability to hide Crowd 6+ version from page Footer
  44. Suggestion
    CWD-6343Add the ability to redirect logout URL to SSO
  45. Suggestion
    CWD-4868Include the limitations of importing users in Crowd Documentation
  46. Suggestion
    CWD-5737"every time the user logs in" Group Membership setting ignored when Nest Groups enabled
  47. Suggestion
    CWD-5740Set 90-day password expiration for single user
  48. Suggestion
    CWD-5788CROWD REST API for /rest/admin/1.0/group-level-admin/ are unclear and need more clarity on usage
  49. Suggestion
    CWD-5808Crowd Server Sizing Recommendations
  50. Suggestion
    CWD-5975Crowd needs to send "User added notifications email" for a new user created through REST API.
Refresh results
1 of 797
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

            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            Support reference count New: 2
            Nate Hansberry made changes -
            Description Original: h3. Problem Definition
            When nested groups is enabled, the expected functionality is not observed until a full sync is performed

            h3. 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
             
            h3. Workaround
            * manual full sync is required             		New: h3. Problem Definition
            When nested groups is enabled, the expected functionality is not observed until a full ldap sync is performed

            h3. 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
             
            h3. Workaround
            * manual full sync is required
            Nate Hansberry created issue -

              Unassigned Unassigned
              nhansberry Nate Hansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: