docs(3149): what the SSO secrets are and where each one lives
The question this answers is "what do I have to configure, and where" — so the table of secrets is the deliverable and the prose is scaffolding around it. The organising idea worth keeping: a secret belongs in-container when nothing outside that container reads it. Every one of authelia's own secrets passes that test; the client secret's plaintext fails it, which is what makes delivery a problem at all rather than a detail.
This commit is contained in:
parent
cdb3c612b2
commit
b4a3eb75b0
3 changed files with 101 additions and 6 deletions
|
|
@ -88,6 +88,12 @@ One authelia, one matrix, one forge per swarm — which host runs them,
|
|||
and what a hive that runs none of them configures instead:
|
||||
[`services.md`](services.md).
|
||||
|
||||
## Single sign-on
|
||||
|
||||
Which secrets the SSO provider generates, which one has a reader in
|
||||
another container, and the three ways that one gets delivered:
|
||||
[`sso.md`](sso.md).
|
||||
|
||||
## The swarm's hive directory
|
||||
|
||||
```nix
|
||||
|
|
|
|||
Loading…
Reference in a new issue