docs: put the credentials prose on the overview and the tables on the reference
The folded-in secrets.md text sat after the reference's table, so the reference was half prose. The overview now holds all the prose (where a secret lives, topologies, the swarm- and hive-level notes, how a reader reaches the store, the browser UI, adding a secret) and the reference holds only the tables, each pointing at the section that explains it. No text dropped; links that asked for the explanation now go to the overview, and the ones that asked for a list or a row go to the reference.
This commit is contained in:
parent
d273fa8028
commit
b53365e371
18 changed files with 618 additions and 593 deletions
|
|
@ -146,13 +146,13 @@ any other session gets `deny`.
|
|||
The container also runs `swarm-secret-publish`, which copies the client
|
||||
secrets authelia mints into the swarm secret store under the secret
|
||||
publisher's own store leaf, handed in as a system credential; see
|
||||
[`credentials-reference.md`](credentials-reference.md). Authelia doesn't wait for it, so the IdP comes up
|
||||
[`credentials.md`](credentials.md). Authelia doesn't wait for it, so the IdP comes up
|
||||
while the store is down, and the publisher retries every 30 seconds. The
|
||||
container's journal forwarder reads its client secret back from the store
|
||||
under the same leaf, and is off where the container has none.
|
||||
|
||||
See [`sso.md`](sso.md) for bootstrapping the first user and the OIDC
|
||||
relying-party flow, and [`credentials-reference.md`](credentials-reference.md) for where authelia
|
||||
relying-party flow, and [`credentials.md`](credentials.md) for where authelia
|
||||
generates and reads each of its keys.
|
||||
|
||||
### Metrics (VictoriaMetrics + Grafana)
|
||||
|
|
@ -193,7 +193,7 @@ authelia ones, and the local login form is always off. Grafana's API still
|
|||
accepts HTTP basic auth for its built-in `admin` account, so that account's
|
||||
password is a random one minted into the swarm secret store
|
||||
(`swarm/services/<grafana client id>/admin/password`) and applied on every
|
||||
Grafana start — see [`credentials-reference.md`](credentials-reference.md).
|
||||
Grafana start — see [`credentials.md`](credentials.md).
|
||||
|
||||
<!-- vale write-good.Passive = YES -->
|
||||
|
||||
|
|
@ -311,7 +311,7 @@ second `swarm-metrics-auth` instance (`swarm-logs-grafana-auth`) on the log
|
|||
store's host checks it against the same store path; the gateway tells it from
|
||||
the others by its shape, 64 hex digits. Anything else needs an operator's
|
||||
authelia session. Because one bearer opens both read APIs, a rotation
|
||||
(see [`credentials-reference.md`](credentials-reference.md)) restarts Grafana once, and the log store
|
||||
(see [`credentials.md`](credentials.md)) restarts Grafana once, and the log store
|
||||
accepts the new value within a minute.
|
||||
|
||||
The collector also scrapes this store's own metrics, at
|
||||
|
|
|
|||
Loading…
Reference in a new issue