Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-400

[RBAC] - Groups and Group members for developer roles

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Minor
    • None
    • SaaS, 2.11.1 GA
    • System

    Description

      Current behavior:
      User with role "Developer accounts" cannot view "Group Memberships"
      User with role "Developer portal" cannot view "Groups"

      The admin provider needs to grant full admin rights to the user to perform the actions.

      Expected results:
      The user with both above roles should be able to perform actions related to developer accounts and developer portal.

      Addition from this comment
      A different customer would like to extend the scope with the following individual and separate permissions:

      Modify developer portal
      Modify swagger files
      Create backends
      Create products
      View logs
      View analytics
      A 'superadmin' with full control

      Attachments

        Issue Links

          is duplicated by

          Feature Request - Feature requests from customers and/or users THREESCALE-7982 [RBAC] Restrict API access by specific User group

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users THREESCALE-1341 Define new roles in 3scale admin console and possibility to map this roles with a RHSSO attribute

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Defined

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-3259 Set permission group for Invite a new Team Member

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              Unassigned Unassigned
              vbhalera@redhat.com Vinay Bhalerao (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: