LLDAP
LLDAP is a lightweight LDAP (Lightweight Directory Access Protocol) server for user authentication and management.
Platform availability
Available on 5 of 10 platforms
- Unraid
- TrueNAS
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
71/100 Good
- Maintained
- 86last commit 56 days ago
- Popular
- 766,604 GitHub stars
- Easy to install
- 755 install platforms, install notes, Docker image
- Light to run
- 95512 MB minimum RAM, runs on ARM
- Security check
- 152 serious findings, 1 minor, CI, tests
Security check: 2 serious findings
- A private key is committed in the source code (example_configs/seafile.md:67)
- Uses lettre 0.11.21, which has a known critical vulnerability (crates.io)
Automated checks on commit 99c510a, 17 Oct 2026. Not an audit.
Availability: platform listings confirmed today, links checked 7 days ago
- GitHub stars
- 6,604
- Open issues
- 151
- Last commit
- 2026-09-26
- Latest release
- v0.6.3
- License
- GPL-3.0
- Activity
- stale
Checked 22 days ago - source: GitHub (lldap/lldap)
Resources & Compatibility
Minimum requirements: 512 MB RAM, 1 CPU core(s), 10 GB disk. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Copy and edit the LLDAP config first Copy the example settings file, lldap_config.toml, to /usr/local/lldap_server/lldap_config.toml and fill in your settings before starting the service. LLDAP uses this file for its basic setup, so missing or wrong values can stop the service or break logins. source
- Start and check the LLDAP service Use systemctl, the Linux service manager, with --user to reload, start lldap, and check its status after setup. If the service is not running, the status output helps you see the problem instead of guessing. source
- Back up users.db and the config Keep a safe copy of users.db, the LLDAP user database, and lldap_config.toml, the settings file, from /usr/local/lldap_server. These files hold your accounts and settings, so losing them can mean losing access or having to set LLDAP up again. source
Fetched 54 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which LLDAP group should I use for service accounts?
Use a user in lldap_strict_readonly or lldap_password_manager for most LDAP integrations. Reserve lldap_admin for people who need full Web UI administration.
How can I check why the LLDAP service is not running after setup?
Run systemctl --user start lldap and then systemctl --user status lldap. If the service is not running, the status output helps identify the problem.
Can LLDAP be paired with Authelia?
Yes, LLDAP can be paired with Authelia.
Answers sourced from github.com, github.com, selfhostindex.com
Community
- LLDAP release v0.4: A Simplified LDAP Server : r/selfhosted - Reddit (reddit)
- Which LDAP is recommended to deploy? : r/selfhosted - Reddit (reddit)
- AD/LDAP for home? : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads