[PR #1205] [MERGED] docs: move authelia configuration to markdown file #1181

New issue

Closed

opened 2026-02-27 09:11:13 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 09:11:13 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/lldap/lldap/pull/1205
Author: @hendrik1120
Created: 7/8/2025
Status: ✅ Merged
Merged: 7/13/2025
Merged by: @nitnelave

Base: main ← Head: docs-authelia

📝 Commits (2)

ded962c docs: move authelia configuration to markdown file
68493c2 docs: add tls configuration

📊 Changes

4 files changed (+42 additions, -38 deletions)

View changed files

📝 example_configs/README.md (+1 -1)
➕ example_configs/authelia.md (+39 -0)
➖ example_configs/authelia_config.yml (+0 -35)
📝 example_configs/seafile.md (+2 -2)

📄 Description

Hi,

this is a bit of an overhaul of the existing authelia configuration for LLDAP.

I recently moved and split up the authelia ldap reference for specific ldap providers to the integration section.
During that, I noticed that the user filter already is configured to allow signing in with username and email.
This was really the main issue with the existing documentation on this side, the other things are mostly QOL.

I removed the configuration options which were already the authelia default to focus more on the LLDAP specific things, which are because of the implementation template quite minimal.

Before removing the additional_users_dn option, I saw that it was introduced by #1182. It is in my opinion highly likely that this was an issue with the authelia helm chart during that time. See PR. The value that was set is the current default for the LLDAP implementation template.

Password change is a relatively new feature introduced in v4.39 so it should be disabled as well if users don't wish to use authelia as a password manager.

I also saw the new PR to disable user logins, at the moment I am not quite sure if that can be integrated in the authelia configuration template for LLDAP without a breaking change, the updated user filter might have to be documented separately.

Sorry for the long explainer, we can also chat on discord if you have any questions or feedback.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/lldap/lldap/pull/1205 **Author:** [@hendrik1120](https://github.com/hendrik1120) **Created:** 7/8/2025 **Status:** ✅ Merged **Merged:** 7/13/2025 **Merged by:** [@nitnelave](https://github.com/nitnelave) **Base:** `main` ← **Head:** `docs-authelia` --- ### 📝 Commits (2) - [`ded962c`](https://github.com/lldap/lldap/commit/ded962c3aae0e4fc7da76aecaf0c03187031f568) docs: move authelia configuration to markdown file - [`68493c2`](https://github.com/lldap/lldap/commit/68493c2ff069beb988eea380760dfd4371e09e3c) docs: add tls configuration ### 📊 Changes **4 files changed** (+42 additions, -38 deletions) <details> <summary>View changed files</summary> 📝 `example_configs/README.md` (+1 -1) ➕ `example_configs/authelia.md` (+39 -0) ➖ `example_configs/authelia_config.yml` (+0 -35) 📝 `example_configs/seafile.md` (+2 -2) </details> ### 📄 Description Hi, this is a bit of an overhaul of the existing authelia configuration for LLDAP. I recently moved and split up the authelia ldap reference for specific ldap providers to the integration section. During that, I noticed that the user filter already is configured to allow signing in with username and email. This was really the main issue with the existing documentation on this side, the other things are mostly QOL. I removed the configuration options which were already the authelia default to focus more on the LLDAP specific things, which are because of the implementation template quite minimal. Before removing the `additional_users_dn` option, I saw that it was introduced by #1182. It is in my opinion highly likely that this was an issue with the authelia helm chart during that time. See [PR](https://github.com/authelia/chartrepo/pull/319/). The value that was set is the current default for the LLDAP implementation template. Password change is a relatively new feature introduced in v4.39 so it should be disabled as well if users don't wish to use authelia as a password manager. I also saw the new PR to disable user logins, at the moment I am not quite sure if that can be integrated in the authelia configuration template for LLDAP without a breaking change, the updated user filter might have to be documented separately. Sorry for the long explainer, we can also chat on discord if you have any questions or feedback. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>