#971 feat: add disable_keyring config option to skip token caching Pull request opened by pingsutw Summary • Adds

admin.disableKeyring

YAML config option (and corresponding

FLYTE_ADMIN_DISABLEKEYRING

env var) to disable system keyring use for auth tokens • Plumbs the flag through

PlatformConfig

→

init_from_config

→

init

→

_initialize_client

→

ClientSet

→

Authenticator

→

KeyringStore.retrieve/store/delete

• When disabled,

KeyringStore

skips all store/retrieve/delete operations so tokens are never persisted to the system keyring Why Useful for environments where the system keyring is unavailable (headless/CI), misconfigured, or undesirable for security reasons. Users can now opt out of token caching via config or env var without having to rely on side-channel hacks. Usage YAML config: admin: endpoint: dns:///your-endpoint authType: Pkce disableKeyring: true Env var:

export FLYTE_ADMIN_DISABLEKEYRING=true

Test plan • Added unit tests in

tests/flyte/keyring/test_keyring_store.py

covering `store`/`retrieve`/`delete` with

disable=True

and

disable=False

• Existing keyring tests still pass • Manually verify with a real endpoint that no tokens are written to the keyring when

disableKeyring: true

is set flyteorg/flyte-sdk