-
Task
-
Resolution: Done
-
Major
-
1.3.1
Description of problem:
Shared content needed for the introduction and misplaced in specicifc chapters.
You can configure Red Hat Developer Hub policy and roles by using different sources. To maintain data consistency, Developer Hub associates each permission policy and role with one unique source. You can only use this source to change the resource.
The available sources are:
Configuration fileConfigure roles and policies in the Developer Hub app-config.yaml configuration file, for instance to declare your policy administrators.
The Configuration file pertains to the default role:default/rbac_admin role provided by the RBAC plugin. The default role has limited permissions to create, read, update, and delete permission policies or roles, and to read catalog entities.
Note | In case the default permissions are insufficient for your administrative requirements, you can create a custom admin role with required permission policies. |
REST API
Configure roles and policies by using the Developer Hub Web UI or by using the REST API.
CSV file
Configure roles and policies by using external CSV files.
Legacy
The legacy source applies to policies and roles defined before RBAC backend plugin version 2.1.3, and is the least restrictive among the source location options.
Important | Replace the permissions and roles using the legacy source by permissions using the REST API or the CSV file sources. |
Procedure * To determine the source of a role or policy, use a GET request.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- <steps>
Actual results:
Expected results:
Reproducibility (Always/Intermittent/Only Once):
Build Details:
Additional info (Such as Logs, Screenshots, etc):
1.
|
[DOC] SME Review | Closed | Fabrice Flore-Thébault | ||
2.
|
[DOC] QE Review | Closed | Unassigned | ||
3.
|
[DOC] Peer Review | Closed | Fabrice Flore-Thébault |