1.7 KiB
title | description | lead | date | draft | images | menu | weight | toc | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Environment | Using the Environment Variable Configuration Method. | Authelia has a layered configuration model. This section describes how to implement the environment configuration. | 2022-06-15T17:51:47+10:00 | false |
|
101300 | true |
Environment variables are applied after the configuration file meaning anything specified as part of the environment overrides the configuration files.
Please Note: It is not possible to configure several sections at this time, these include but may not be limited to the rules section in access control, the clients section in the OpenID Connect 1.0 Provider, the cookies section of in session, and the authz section in the server endpoints.
Prefix
The environment variables must be prefixed with AUTHELIA_
. All environment variables that start with this prefix must
be for configuration. Any supplied environment variables that have this prefix and are not meant for configuration will
likely result in an error or even worse misconfiguration.
Kubernetes
Please see the Kubernetes Integration: Enable Service Links documentation for specific requirements for using Authelia with Kubernetes.
Mapping
Configuration options are mapped by their name. Levels of indentation / subkeys are replaced by underscores.
For example this YAML configuration:
log:
level: 'info'
server:
buffers:
read: 4096
Can be replaced by this environment variable configuration:
AUTHELIA_LOG_LEVEL=info
AUTHELIA_SERVER_BUFFERS_READ=4096
Environment Variables
{{% table-config-keys secrets="false" %}}