-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
quay-v3.10.2
Customer is reporting that the GLOBAL_READONLY_SUPER_USERS is not working as expected.
I tried to reproduce and here is my outcome
config.yaml
SERVER_HOSTNAME: quay-enterprise.apps.duda-ocp4.emea.aws.cee.support
SETUP_COMPLETE: true
SUPER_USERS:
- quayadmin
GLOBAL_READONLY_SUPER_USERS:
- duda
FEATURE_UI_V2: true
FEATURE_USER_INITIALIZE: true
BROWSER_API_CALLS_XHR_ONLY: false
FEATURE_SUPERUSERS_FULL_ACCESS: true
SEARCH_MAX_RESULT_PAGE_COUNT: 30
SEARCH_RESULTS_PER_PAGE: 30
I had created 2 users , duda and eduardo
the user duda is listed under the GLOBAL_READONLY_SUPER_USERS on my understanding this user should had readonly on whole registry, but it is not working on both UIs.
- incorporates
-
RFE-4510 Team Role that allows token access but doesn't allow create. (A limited "admin" type role)
- Rejected
- is related to
-
PROJQUAY-2604 Ability to create users with read-only global access
- Closed
-
PROJQUAY-8023 GLOBAL_READONLY_SUPER_USERS doesn't work for /v2/_catalog endpoint
- Closed
- relates to
-
PROJQUAY-6980 Add support for a global read only superuser
- Closed