You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
config-manager: a kind for the OAuth2 clients no application owns (not started; after the password convention) #1344
Part of the tracking issue #1254. Maintainer decision (2026-11-16): OAuth2Client gets a kind of its own (K), after the password convention (decided, below) and when the maintainer orders it. NOT STARTED: this issue only holds the disposition.
OAuth2 clients are represented twice and unevenly: the clients that an application owns by the applications kind (config-manager keeps everything an application owns in one folder), and every other client only through oauth2-agents by name (no discovery of the clients no application owns, no delete kind; the delete of applications removes owned clients only). It is the only type with a skip rule today (a client an application owns is skipped by oauth2-agents in a tree that uses the application layout). The library blacklists the type from the generic discovery.
A discovery kind for the clients that no application owns, reusing the ownership index of the applications kind, with pull, push, delete and a pull all step, a skip entry in the shared table, and the secret handled by the convention below.
For any kind of a password-bearing type (the OAuth2 client secret, IG, Java, Web, 2.2_Agent, SharedAgent): AM does not return the secret; the placeholder name derives from the object (${<ID>_PASSWORD}, named like the ESV rule esvToEnv in src/utils/FrConfig.ts); a missing variable fails the push naming it (as record 0042 says for applications); a pull without an override warns. Placeholders are filled from -E/--env, --env-file and, on config-manager push, the process environment.
Activity