Update docs/content/concepts/authorization/authorizers.md

Co-authored-by: Marvin Beckers <mail@embik.me>
kcp-dev · Feb 7, 2025 · 8774ce6 · 8774ce6
1 parent 76fe182
commit 8774ce6
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/docs/content/concepts/authorization/authorizers.md b/docs/content/concepts/authorization/authorizers.md
@@ -282,10 +282,10 @@ The webhook will receive JSON-marshalled `SubjectAccessReview` objects, that (co
 
 By default, the authorizers are evaluated in the following order:
 
-1. **Always Allow Groups Authorizer**
-2. **Always Allow Paths Authorizer**
-3. **RBAC Chain**
-4. **Webhook Authorizer**
+1. **Always Allow Groups Authorizer** (`AlwaysAllowGroups`)
+2. **Always Allow Paths Authorizer** (`AlwaysAllowPaths`)
+3. **RBAC Chain** (`RBAC`)
+4. **Webhook Authorizer** (`Webhook`)
 
 The order in which authorizers are evaluated can be configured. This allows administrators to customize the authorization flow.
 It can be done by setting `--authorization-order` flag in the kcp server. This flag accepts a comma-separated list of authorizer names, which will be evaluated in the specified order.