Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-432

Client applications should only see groups which have been allocated to them

XMLWordPrintable

    • 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.

      Atlassian Status as of 31 October 2013

      Hi everyone,

      Thank you for your votes and comments on this improvement request. Whilst this is something we would like to implement some day, it is not at the forefront of our upcoming backlog.

      We will be focussing on improving the integration of Crowd within our Atlassian suite of products, as well as simplifying and improving the overall user management and a unified administrative experience.

      If our backlog changes and this improvement request becomes a priority, this ticket will be updated. If you'd like to better understand how we make roadmap decisions, have a read of : https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy

      Cheers, Helen Hung
      Atlassian Product Management

      Currently, a client application can "see" all the groups in the directories configured for that application.

      Ideally, if Allow All To Authenticate on a directory is set to False, only the configured groups should be visible to the application. If Allow All To Authenticate on a directory is set to True, then the current behaviour of retrieving all groups is acceptable.

            [CWD-432] Client applications should only see groups which have been allocated to them

            Thiago Masutti made changes -
            Remote Link Original: This issue links to "KRAK-452 (JIRA Server (Bulldog))" [ 265640 ] New: This issue links to "KRAK-2440 (JIRA Server (Bulldog))" [ 265640 ]
            Pawel Gruszczynski (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Under Consideration [ 11774 ] New: Closed [ 6 ]
            Pawel Gruszczynski (Inactive) made changes -
            Link New: This issue duplicates CWD-5145 [ CWD-5145 ]

            Pawel Gruszczynski (Inactive) added a comment - - edited

            The feature has been already released in Crowd 4.4:

            https://confluence.atlassian.com/crowd/crowd-4-4-release-notes-1087517293.html

            Pawel Gruszczynski (Inactive) added a comment - - edited The feature has been already released in Crowd 4.4: https://confluence.atlassian.com/crowd/crowd-4-4-release-notes-1087517293.html

            Florian Reichl added a comment -

            Same with me!

            Florian Reichl added a comment - Same with me!
            Pawel Gruszczynski (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 492826 ]
            JayBe (Inactive) made changes -
            Labels Original: cl New: cl kcs-flagged

            Kumaran added a comment -

            I can understand that this feature request is on backlog for 13 years now. With growing user base and big companies working on large scale, plugins, custom fields look ups on large group set and membership of all groups impact performance of atlassian tools. I would strongly ask the current product manager to consider implementing this feature. Thank you !

            Kumaran added a comment - I can understand that this feature request is on backlog for 13 years now. With growing user base and big companies working on large scale, plugins, custom fields look ups on large group set and membership of all groups impact performance of atlassian tools. I would strongly ask the current product manager to consider implementing this feature. Thank you !

            Anurag Jalan added a comment -

            Same issue at our end also. We have integrated Crowd with JIRA, Jira Service Desk, Confluence & Bitbucket. What we now see is that all groups configured in Crowd is visible in all applications which is not required. This causes confusion among Atlassian Administrators who are distributed across various locations. Appreciate if it can be fixed.

            Anurag Jalan added a comment - Same issue at our end also. We have integrated Crowd with JIRA, Jira Service Desk, Confluence & Bitbucket. What we now see is that all groups configured in Crowd is visible in all applications which is not required. This causes confusion among Atlassian Administrators who are distributed across various locations. Appreciate if it can be fixed.
            Monique Khairuliana (Inactive) made changes -
            Link New: This issue is duplicated by CWD-5267 [ CWD-5267 ]

              Unassigned Unassigned
              shamid@atlassian.com shihab
              Votes:
              60 Vote for this issue
              Watchers:
              41 Start watching this issue

                Created:
                Updated:
                Resolved: