a removed hive's OIDC client secret is deleted with its other store credentials
This commit is contained in:
parent
b21a3e3632
commit
2eacb83b21
1 changed files with 104 additions and 39 deletions
|
|
@ -57,7 +57,10 @@ For each such hive, in this order:
|
|||
1. delete its `swarm-hive` forge token,
|
||||
2. remove its account from the `agent-configs/hives` team,
|
||||
3. delete the store secret `swarm/hives/<hive>/forge/token`,
|
||||
4. delete the cert-auth role `hive-<hive>`.
|
||||
4. delete the store secret `swarm/hives/<hive>/oidc/client`, the hive's queue
|
||||
client secret (authelia's client for the hive leaves the config on the
|
||||
rebuild that drops it; the stored plaintext doesn't),
|
||||
5. delete the cert-auth role `hive-<hive>`.
|
||||
|
||||
The role goes last because it marks that work remains: a step that fails
|
||||
leaves the role, and the next pass runs every step again. A step that finds
|
||||
|
|
@ -72,8 +75,10 @@ swarm-controller writes at start.
|
|||
Nothing happens when the roster didn't load. An unset or unparseable
|
||||
`SWARM_CONTROLLER_HIVES`, and a roster with no hive, read the same as a removal of every
|
||||
hive, so the controller logs an error at start and skips the
|
||||
cut-off. The attic pull token and the OIDC client secret under
|
||||
`swarm/hives/<hive>/` stay, as does the forge account itself.
|
||||
cut-off. The attic pull token under `swarm/hives/<hive>/` stays, as does the
|
||||
forge account itself. The pull token is one swarm-wide token copied to each
|
||||
hive; a copy a removed hive already holds keeps working, read-only, until someone rotates the
|
||||
cache's signing key.
|
||||
|
||||
## Per-agent forge accounts
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue