-
Bug
-
Resolution: Unresolved
-
Normal
-
1.2.2, 1.3, 1.4
-
None
-
8
-
False
-
-
False
-
-
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
- Enable the topology plugin
- Add the topology plugin to the list of `pluginsWithPermissions`
- Enable the rbac frontend plugin
- Give yourself admin access
- Navigate to the admin page of the rbac plugin
- Attempt to create a role and permission using the `topology.view.read` permission
- 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.
- account is impacted by
-
RHIDP-4253 RBAC - Configure permissions from other plugins like tekton or topology using web console I tried to use "pluginsWithPermission" but unsuccessfully
- Closed
- links to