From 37630e889da5db96b55a6d6dc338e09272bbba3f Mon Sep 17 00:00:00 2001 From: Frank Villaro-Dixon Date: Thu, 4 Dec 2025 09:59:25 +0100 Subject: [PATCH] `GLOBAL_READONLY_SUPER_USERS`: fix typo Remove the "Only works for those superusers defined with the `SUPER_USERS` configuration field." as this is not true, and if done, would make the user a super user. Signed-off-by: Frank Villaro-Dixon --- modules/config-fields-user.adoc | 2 +- modules/config-preconfigure-automation.adoc | 2 +- modules/config-updates-38.adoc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/config-fields-user.adoc b/modules/config-fields-user.adoc index 7c64e063b..b4067f035 100644 --- a/modules/config-fields-user.adoc +++ b/modules/config-fields-user.adoc @@ -72,7 +72,7 @@ The user configuration fields define how user accounts behave in your {productna | **RESTRICTED_USERS_WHITELIST** | String | When set with `FEATURE_RESTRICTED_USERS: true`, specific users are excluded from the `FEATURE_RESTRICTED_USERS` setting. -| **GLOBAL_READONLY_SUPER_USERS** | String | When set, grants users of this list read access to all repositories, regardless of whether they are public repositories. Only works for those superusers defined with the `SUPER_USERS` configuration field. +| **GLOBAL_READONLY_SUPER_USERS** | List | When set, grants users of this list read access to all repositories, regardless of whether they are public repositories. |=== diff --git a/modules/config-preconfigure-automation.adoc b/modules/config-preconfigure-automation.adoc index add06348f..7df53886a 100644 --- a/modules/config-preconfigure-automation.adoc +++ b/modules/config-preconfigure-automation.adoc @@ -16,7 +16,7 @@ Unlike all other registry API calls that require an link:https://docs.redhat.com | *BROWSER_API_CALLS_XHR_ONLY* |Boolean | Controls whether the registry API only accepts calls from browsers. To allow general browser-based access to the API, administrators must set this field to `False`. If set to `True`, API calls are blocked, preventing both administrators and users from interacting with the API. -| *SUPER_USERS* |String | Defines a list of administrative users, or superusers, who have full privileges and unrestricted access to the registry. {productname} administrators should configure `SUPER_USERS` in the `config.yaml` before deployment to ensure immediate administrative access without requiring a redeploy. Setting this field post-deployment requires restarting the registry to take effect. +| *SUPER_USERS* |List | Defines a list of administrative users, or superusers, who have full privileges and unrestricted access to the registry. {productname} administrators should configure `SUPER_USERS` in the `config.yaml` before deployment to ensure immediate administrative access without requiring a redeploy. Setting this field post-deployment requires restarting the registry to take effect. | *FEATURE_USER_CREATION* |Boolean | Relegates the creation of new users to only superusers when this field is set to `False`. This setting is useful in controlled environments where user access must be provisioned manually by administrators. |=== diff --git a/modules/config-updates-38.adoc b/modules/config-updates-38.adoc index e90b7a4d3..1b17395c1 100644 --- a/modules/config-updates-38.adoc +++ b/modules/config-updates-38.adoc @@ -29,7 +29,7 @@ With this field, administrators can add or remove superusers without having to u *Default:* `False` -| xref:configuring-global-readonly-super-users[**GLOBAL_READONLY_SUPER_USERS**] | String | When set, grants users of this list read access to all repositories, regardless of whether they are public repositories. +| xref:configuring-global-readonly-super-users[**GLOBAL_READONLY_SUPER_USERS**] | List | When set, grants users of this list read access to all repositories, regardless of whether they are public repositories. | xref:configuring-feature-restricted-users[**FEATURE_RESTRICTED_USERS**] | Boolean | When set with `RESTRICTED_USERS_WHITELIST`, restricted users cannot create organizations or content in their own namespace. Normal permissions apply for an organization's membership, for example, a restricted user will still have normal permissions in organizations based on the teams that they are members of.