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

Permissions visibility across all Atlassian products in Crowd

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

      Today, you can assign your users to groups in Crowd. This impacts permissions and defines who can authenticate to your products, but does not provide visibility into whether a user has access to a specific Jira project, Confluence space or Bitbucket repository.

      As an admin I would like to see and manage in future all of my users permissions across my Atlassian products in a single location.

      I would like to see to which specific applications a user has access among my Atlassian products. This would include access to specific projects, spaces and seeing the impact of adding a user to a group with its permission schemes.

            [CWD-5217] Permissions visibility across all Atlassian products in Crowd

            KentGran added a comment -

            Just wrote and posted this in the forum:

            Hi all!

            Started to look at Crowd since I’m administrating users and groups for JIRA, Confluence, Bitbucket, Sonatype Nexus and Jenkins.

             

            They are all connected to an LDAP where users and groups are defined. It works reasonably fine most of the time but as the number of projects, spaces, jobs, users and groups tend to increase over time, so does the complexity of administering permissions/rights, group assignments, etc, etc. Managing users and groups in one central point is fine but it requires discipline at all times regarding group names, where they are assigned, no shortcuts to be taken during stressful situations where you can see that the easiest way to resolve a certain situation is to assign an already existing group to a project/job/space even though it doesn’t follow the strict naming conventions you want (or what ever the rule is)

             

            Having said all this, to my understanding, Crowd is lacking the functionality/ability to get hold of, an present, where a certain group, or individual user for that matter, is assigned inside any of the applications it is connected to. Is that the case or am I missing something here? Administering only users and groups is just part of the problem. If one is to get the full picture, one need to know where users and groups are used/assigned in the applications (JIRA, Confluence, Jenkins, etc…). And not just the applications, the project/space/job, etc. A much higher level of granularity is needed in order to to get the big picture.

             

            I can see an opening for a plugin here if my description is accurate and valid. I would certainly help in implementing such app/plugin if anyone would like to take on such challenge. However, I’m a C/C++ hacker myself with not to much JAVA knowledge so I wouldn’t be able to do this on my own.

             

            Any takers?

             

            Regards

            Kent Granstrom

            KentGran added a comment - Just wrote and posted this in the forum: Hi all! Started to look at Crowd since I’m administrating users and groups for JIRA, Confluence, Bitbucket, Sonatype Nexus and Jenkins.   They are all connected to an LDAP where users and groups are defined. It works reasonably fine most of the time but as the number of projects, spaces, jobs, users and groups tend to increase over time, so does the complexity of administering permissions/rights, group assignments, etc, etc. Managing users and groups in one central point is fine but it requires discipline at all times regarding group names, where they are assigned, no shortcuts to be taken during stressful situations where you can see that the easiest way to resolve a certain situation is to assign an already existing group to a project/job/space even though it doesn’t follow the strict naming conventions you want (or what ever the rule is)   Having said all this, to my understanding, Crowd is lacking the functionality/ability to get hold of, an present, where a certain group, or individual user for that matter, is assigned inside any of the applications it is connected to. Is that the case or am I missing something here? Administering only users and groups is just part of the problem. If one is to get the full picture, one need to know where users and groups are used/assigned in the applications (JIRA, Confluence, Jenkins, etc…). And not just the applications, the project/space/job, etc. A much higher level of granularity is needed in order to to get the big picture.   I can see an opening for a plugin here if my description is accurate and valid. I would certainly help in implementing such app/plugin if anyone would like to take on such challenge. However, I’m a C/C++ hacker myself with not to much JAVA knowledge so I wouldn’t be able to do this on my own.   Any takers?   Regards Kent Granstrom

              Unassigned Unassigned
              mradochonski@atlassian.com Marek Radochonski (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: