230db5ad7e
Adds config/providers_oauth2/vault.yaml so human logins to OpenBao go
through Authentik SSO (bao CLI and the web UI). Machine auth (approle,
kubernetes, CI) and break-glass are unchanged and stay on the OpenBao side.
Extends the oauth2 provider module so a config may generate its own client
secret instead of reading a pre-seeded one: client_secret_vault.generate
creates a random_password and writes {client_id, client_secret} to the given
kv-v2 path. Providers without the flag keep the existing read-only data source
behaviour. This is what lets the provider land with no manual Vault seed.
Gates the new application with akP-vault-admin and nests it in
akR-global-admin, matching how every other app in this repo is bound.
6 lines
300 B
YAML
6 lines
300 B
YAML
# Permission group akP-vault-admin (name = filename). Gates the OpenBao
|
|
# application: without a binding every Authentik user could complete an OIDC
|
|
# login, so access is restricted to this group. OpenBao's own policy mapping
|
|
# keys off the same group name in the ak_groups claim.
|
|
application: vault
|