Skip to content

GLOBAL_READONLY_SUPER_USERS: fix typo #1485

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Frankkkkk wants to merge 1 commit into
base: master
Choose a base branch
from
Open

GLOBAL_READONLY_SUPER_USERS: fix typo #1485

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/config-fields-user.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

|===

Expand Down
2 changes: 1 addition & 1 deletion modules/config-preconfigure-automation.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
|===
Expand Down
2 changes: 1 addition & 1 deletion modules/config-updates-38.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down