README: use same secret length in example as official docs
Upstream documentation uses 60 bytes: https://docs.goauthentik.io/docs/install-config/install/docker-compose#preparation Originally the length here was taken from the upstream Makefile: https://github.com/goauthentik/authentik/blob/version/2023.5.1/Makefile#L29
This commit is contained in:
parent
48fda0cade
commit
e877502737
1 changed files with 1 additions and 1 deletions
|
|
@ -51,7 +51,7 @@ Example configuration:
|
||||||
|
|
||||||
The `environmentFile` option references a systemd [EnvironmentFile](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#EnvironmentFile=), that needs to be placed on the same host as authentik and should only be accessible to root. Secrets can be specified in this environment file without causing them to be placed in the world-readable /nix/store. Note that `pkgs.writeText` and similar tooling also causes secrets to be placed in the /nix/store.
|
The `environmentFile` option references a systemd [EnvironmentFile](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#EnvironmentFile=), that needs to be placed on the same host as authentik and should only be accessible to root. Secrets can be specified in this environment file without causing them to be placed in the world-readable /nix/store. Note that `pkgs.writeText` and similar tooling also causes secrets to be placed in the /nix/store.
|
||||||
|
|
||||||
After generating a secret key for authentik, for example using `openssl rand -base64 32` the file's contents should look like this:
|
After generating a secret key for authentik, for example using `openssl rand -base64 60` the file's contents should look like this:
|
||||||
|
|
||||||
```
|
```
|
||||||
AUTHENTIK_SECRET_KEY=<generated secret key>
|
AUTHENTIK_SECRET_KEY=<generated secret key>
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue