Skip to content

Commit 00dc6f7

Browse files
themr0cjmagak
andauthored
RHIDP-4896 Determining the permission policy configuration source (redhat-developer#705)
Co-authored-by: jmagak <[email protected]>
1 parent 8a0575b commit 00dc6f7

2 files changed

+42
-7
lines changed

assemblies/assembly-configuring-authorization-in-rhdh.adoc

+9-7
Original file line numberDiff line numberDiff line change
@@ -16,20 +16,22 @@ the {product-short} RBAC feature allows you
1616
to define policies in a declarative fashion using a simple CSV based format.
1717
You can define the policies by using {product-short} web interface or REST API, rather than editing the CSV directly.
1818

19-
To apply RBAC in {product-short}:
19+
To define authorizations in {product-short}:
2020

21-
. The {product-short} administrator sets up the RBAC feature:
22-
.. Enable the RBAC feature
23-
.. Configure Policy Administrators
21+
. The {product-short} administrator enables and gives access to the RBAC feature.
2422

25-
. The {product-short} policy administrator configures your RBAC policies:
26-
.. Define roles with specific permissions
27-
.. Assign the roles to users and groups
23+
. You define your roles and policies by combining the following methods:
2824

25+
* The {product-short} policy administrator uses the {product-short} web interface or REST API.
26+
* The {product-short} administrator edits the main {product-short} configuration file.
27+
* The {product-short} administrator edits external files.
2928

3029
include::modules/authorization/proc-enabling-the-rbac-plugin.adoc[leveloffset=+1]
3130

3231

32+
include::modules/authorization/proc-determining-permission-policy-and-role-configuration-source.adoc[leveloffset=+1]
33+
34+
3335
include::assembly-managing-authorizations-by-using-the-rhdh-web-ui.adoc[leveloffset=+1]
3436

3537

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
[id='proc-determining-policy-and-role-source']
2+
= Determining permission policy and role configuration source
3+
4+
You can configure {product} policy and roles by using different sources.
5+
To maintain data consistency, {product-short} associates each permission policy and role with one unique source.
6+
You can only use this source to change the resource.
7+
8+
The available sources are:
9+
10+
Configuration file::
11+
Configure roles and policies in the {product-short} `app-config.yaml` configuration file, for instance to xref:enabling-and-giving-access-to-rbac[declare your policy administrators].
12+
+
13+
The Configuration file pertains to the default `role:default/rbac_admin` role provided by the RBAC plugin.
14+
The default role has limited permissions to create, read, update, delete permission policies or roles, and to read catalog entities.
15+
+
16+
[NOTE]
17+
====
18+
In case the default permissions are insufficient for your administrative requirements, you can create a custom admin role with the required permission policies.
19+
====
20+
21+
REST API::
22+
Configure roles and policies xref:managing-authorizations-by-using-the-web-ui[by using the {product-short} Web UI] or by using the REST API.
23+
24+
CSV file::
25+
Configure roles and policies by using external CSV files.
26+
27+
Legacy::
28+
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.
29+
+
30+
IMPORTANT: Replace the permissions and roles using the legacy source with the permissions using the REST API or the CSV file sources.
31+
32+
.Procedure
33+
* To determine the source of a role or policy, use a `GET` request.

0 commit comments

Comments
 (0)