RHIDP-1848: Updates the setting up RBAC permission

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

@@ -28,6 +28,7 @@ To define authorizations in {product-short}:
 
 include::modules/authorization/proc-enabling-the-rbac-plugin.adoc[leveloffset=+1]
 
+include::modules/authorization/proc-enabling-guest-access-for-rbac-frontend-plugin.adoc[leveloffset=+2]
 
 include::modules/authorization/proc-determining-permission-policy-and-role-configuration-source.adoc[leveloffset=+1]
 

modules/authorization/proc-enabling-guest-access-for-rbac-frontend-plugin.adoc

@@ -0,0 +1,58 @@
+[id="enabling-guest-access-for-the-rbac-frontend-plugin_{context}"]
+= Enabling guest access for the RBAC frontend plugin
+
+Use guest access for the Role-Based Access Control (RBAC) frontend plugin to test and develop, except in production. To enable the guest access for the RBAC frontend, configure the backend plugin and set up the guest authentication provider.
+
+.Prerequisites
+* You have installed the `@janus-idp/backstage-plugin-rbac` plugin in {product-short}. For more information, see link:{plugins-configure-book-url}[{plugins-configure-book-title}].
+
+.Procedure
+
+To configure the RBAC backend plugin, complete the following steps:
+
+Update the `app-config.yaml` file to enable the permission framework as shown:
+
+[source,yaml,subs=+quotes]
+----
+permission
+  enabled: true
+  rbac:
+    admin:
+      users:
+        - name: user:default/guest
+    pluginsWithPermission:
+      - catalog
+      - permission
+      - scaffolder
+----
+
+[NOTE]
+====
+The `pluginsWithPermission` section of the `app-config.yaml` section includes only three plugins by default. Update the section as needed to include any additional plugins that also incorporate permissions.
+====
+
+== Setting up the guest authentication provider
+
+.Procedure
+
+To enable guest authentication and to use it alongside the RBAC frontend plugin, complete the following step:
+
+* In the `app-config.yaml` file, add the user entity reference to resolve and enable the `dangerouslyAllowOutsideDevelopment` option, as shown in the following example:
+
+[source,yaml,subs="+attributes,+quotes"]
+----
+auth:
+  environment: development
+  providers:
+    guest:
+      userEntityRef: user:default/guest
+      dangerouslyAllowOutsideDevelopment: true
+----
+
+[NOTE]
+====
+You can use `user:default/guest` as the user entity reference to match the added user under the `permission.rbac.admin.users` section of the `app-config.yaml` file.
+====
+
+
+