Describe the bugThese four keys are not placed in the correct dict path to configure Postgres TLS settings for Django.
To Reproduce
Deploy Authentik with any Postgres TLS setting configured. For example, client TLS auth or the server auth root CA with TLS verification enabled.
Observe that connections and migration checks (which do not run via Django) complete successfully, but Django ignores these settings (leading to an immediate crash in most cases).
Expected behavior
Authentik should start with these settings configured.
I haven't been able to find anything in the django docs that specifically mentions these values, but several search results show + testing shows that this is the correct config.
Describe the bug These four keys are not placed in the correct dict path to configure Postgres TLS settings for Django.
To Reproduce
Expected behavior
Authentik should start with these settings configured.
Screenshots N/A
Logs
Version and Deployment (please complete the following information):
Additional context
These keys need to be listed under
OPTIONS
, in lower case, as shown here.To workaround this, a patch can be created via
user_settings.py
that can fix the issue. Example of how to deploy this here.