Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-3396

Topology plugin permission does not show up in rbac frontend ui

Prepare for Y ReleasePrepare for Z ReleaseRemove QuarterXMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 1.5
    • 1.2.2, 1.3, 1.4
    • None
    • 8
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework's well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include Topology (`topology.view.read`), Tekton (`tekton.view.read`), ArgoCD (`argocd.view.read`), and Quay (`quay.view.read`).
      Show
      Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework's well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include Topology (`topology.view.read`), Tekton (`tekton.view.read`), ArgoCD (`argocd.view.read`), and Quay (`quay.view.read`).
    • Known Issue
    • Done
    • RHDH Plugins 3261, RHDH Plugins 3265, RHDH Plugins 3266, RHDH Plugins 3267

      Description of problem:

      If the topology plugin has been enabled in the rhdh instance and also added to the app-config so that the permission will be discoverable, it does not show up in the UI.

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Enable the topology plugin
      2. Add the topology plugin to the list of `pluginsWithPermissions`
      3. Enable the rbac frontend plugin
      4. Give yourself admin access
      5. Navigate to the admin page of the rbac plugin
      6. Attempt to create a role and permission using the `topology.view.read` permission
      7. Notice that topology is not an option for a plugin

      Actual results:

      The inability to create a role with the topology plugin permission from the frontend

      Expected results:

      The ability to create a role with the topology plugin permission from the frontend

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      There is a workaround in which you have to call the rbac backend plugin api directly or declare through the use of the CSV file to add the `topology.view.read` permission. I have a suspicion that this is because the Topology plugin does not have a backend plugin, in which we are unable to query for the permissions that this plugin might have.

              rh-ee-dzemanov Dominika Zemanovicova
              rh-ee-pknight Patrick Knight
              RHIDP - Plugins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: