[SCM] Store Auth Config in System Namespace of SecureStore
Description
Currently, SCM Auth configurations are stored in secure store in the namespace in which the repository is configured, but this strongly couples the repository configuration permissions to secure store permissions (i.e. anybody who can read from secure store can also read the repository authentication credentials). We should instead store repository authentication configurations in the system namespace of secure store.
Release Notes
None
100% Done
Activity
Show:
Dennis Li October 20, 2023 at 7:56 PM
Updated the Jira ticket to reflect the current state of affairs.
Dennis Li April 19, 2023 at 3:41 AM
Edited
There are two options for this:
Decouple the auth and repository manager abstractions
Move execution of repository operations to system pods
Pinned fields
Click on the next to a field label to start pinning.
Currently, SCM Auth configurations are stored in secure store in the namespace in which the repository is configured, but this strongly couples the repository configuration permissions to secure store permissions (i.e. anybody who can read from secure store can also read the repository authentication credentials). We should instead store repository authentication configurations in the system namespace of secure store.