Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/authentication.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,9 +122,9 @@ issue a new one.
proxy, set `FANOUT_TRUSTED_PROXY_CIDRS`; otherwise every request shares the
proxy's address and one limit, and other traffic can block recovery.

Fanout contacts the identity provider's discovery endpoint when the server
starts, and exits if that fails. Break-glass access therefore needs a server
that is already running; do not restart Fanout during the outage.
Fanout starts while the identity provider is unavailable, so break-glass access
also works after a restart during the outage. See
[Provider availability](#provider-availability).

### User account API

Expand Down
5 changes: 2 additions & 3 deletions site/src/content/docs/docs/concepts/authentication.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -161,9 +161,8 @@ docker exec fanout fanout login-link --break-glass admin@example.com

Set `FANOUT_AUTH_CODE_SECRET` with at least 32 characters before you need this.
OIDC mode does not require it at startup, but without it the command fails and
the server keeps login links disabled. The server must also be running already:
Fanout contacts the provider's discovery endpoint at startup and exits if that
fails.
the server keeps login links disabled. Fanout starts while the provider is
unavailable, so this also works after a restart during the outage.

The command refuses other roles, suspended users and local mode. The URL expires
in 15 minutes and works once. In OIDC mode, the server accepts only these links
Expand Down
Loading