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

Restrict Admin Access to a Specific Application

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Applications
    • None
    • 4

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

      Current Limitation

      Currently there is only a single level of Crowd Administrator, where the administrator can add, remove, and edit any Application that is configured in Crowd.

      Suggestion

      It would be good if there is another level of Application Administrator which allows a specific group/user to be able to administer the specific application that is assigned, for example:

      1. Mapping a Directory to the Application
      2. Specifying which Groups can access to the Application
      3. Modifying the Automatically Assigned Group options for the application

      This suggestion was previously closed as a duplicate of CWD-4389 but has been re-opened as the released feature is different than this request.

      Example Use Case

      For example: When I log into the Admin Console I can change all applications we have defined in Crowd. That makes sense because I'm a full Admin. The option to make an Admin restricted to a specific Crowd Application would be great. e.g. an Admin that could do everything but only for a specific Application.

            [CWD-4390] Restrict Admin Access to a Specific Application

            SET Analytics Bot made changes -
            Support reference count New: 4
            Damien Tan made changes -
            Component/s New: Applications [ 58995 ]
            Damien Tan made changes -
            Resolution Original: Duplicate [ 3 ]
            Status Original: Closed [ 6 ] New: Gathering Interest [ 11772 ]
            Damien Tan made changes -
            Description Original: It would be great if we could limit access to Applications for Users that log into the Crowd Administration Console.

            *For example:* When I log into the Admin Console I can change all applications we have defined in Crowd. That makes sense because I'm a full Admin. The option to make an Admin restricted to a specific Crowd Application would be great. e.g. an Admin that could do everything but only for a specific Application.             		New: h3. Current Limitation
            Currently there is only a single level of Crowd Administrator, where the administrator can add, remove, and edit *any Application* that is configured in Crowd.


            h3. Suggestion
            It would be good if there is another level of *Application Administrator* which allows a specific group/user to be able to administer the specific application that is assigned, for example:
            # [Mapping a Directory to the Application|https://confluence.atlassian.com/crowd/mapping-a-directory-to-an-application-18579599.html]
            # [Specifying which Groups can access to the Application|https://confluence.atlassian.com/crowd/specifying-which-groups-can-access-an-application-25788430.html]
            # Modifying the [Automatically Assigned Group|https://confluence.atlassian.com/crowd/automatically-assigning-users-to-groups-194806197.html] options for the application


            (i) This suggestion was previously closed as a duplicate of CWD-4389 but has been re-opened as the released feature is different than this request.

            h3. Example Use Case
            *For example:* When I log into the Admin Console I can change all applications we have defined in Crowd. That makes sense because I'm a full Admin. The option to make an Admin restricted to a specific Crowd Application would be great. e.g. an Admin that could do everything but only for a specific Application.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3363165 ] New: JAC Suggestion Workflow 3 [ 3626840 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1392322 ] New: JAC Suggestion Workflow [ 3363165 ]
            Issue Type Original: New Feature [ 2 ] New: Suggestion [ 10000 ]
            Marcin Kempa made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Marcin Kempa made changes -
            Link New: This issue relates to CWD-2318 [ CWD-2318 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 873323 ] New: Simplified Crowd Development Workflow v2 [ 1392322 ]

            Eduardo Mallmann (Inactive) added a comment -

            Hey scott.bitterman, I believe these requests are a bit different, since Don's request seems to be related to the ability to specify a user to be admin in a certain group, so they would be able to add and remove users from the group.

            This feature request is a bit different, since the idea would be to restrict the user to see/edit specific applications in Crowd, so they would manage other settings besides the groups. e.g. add another directory to the application and so on.

            I hope it clarifies.

            Eduardo Mallmann (Inactive) added a comment - Hey scott.bitterman , I believe these requests are a bit different, since Don's request seems to be related to the ability to specify a user to be admin in a certain group, so they would be able to add and remove users from the group. This feature request is a bit different, since the idea would be to restrict the user to see/edit specific applications in Crowd, so they would manage other settings besides the groups. e.g. add another directory to the application and so on. I hope it clarifies.

              Unassigned Unassigned
              emallmann Eduardo Mallmann (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: