Ldap-auth
Ldap-auth software is for authenticating users who request protected resources from servers proxied by nginx. It includes a daemon (ldap-auth) that communicates with an authentication server, and a webserver daemon that generates an authentication cookie based on the user’s credentials. The daemons are written in Python for use with a Lightweight Directory Access Protocol (LDAP) authentication server (OpenLDAP or Microsoft Windows Active Directory 2003 and 2012).
Image details
Source details
Configuration
TypeContainerlinuxlinuxserver/ldap-auth:latest8888:8888/tcp9000:9000/tcp/config : /srv/lsio/ldap-auth/configPUID=1000PGID=1000TZ=Etc/UTCFERNETKEY=CERTFILE=KEYFILE=unless-stoppedTemplate by technorabilia
Notes
Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.
mkdir -p /srv/lsio/ldap-auth/config
Installation
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select the app you wish to deploy, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
docker run -d --name Ldap-auth \
-p 8888:8888/tcp \
-p 9000:9000/tcp \
-e 'PUID=1000' \
-e 'PGID=1000' \
-e 'TZ=Etc/UTC' \
-e 'FERNETKEY=' \
-e 'CERTFILE=' \
-e 'KEYFILE=' \
-v /srv/lsio/ldap-auth/config:/config \
--restart=unless-stopped \
linuxserver/ldap-auth:latestSave this file as compose.yaml and run docker compose up -d
Use this only as a guide.
services:
ldap-auth:
image: linuxserver/ldap-auth:latest
ports:
- 8888:8888/tcp
- 9000:9000/tcp
volumes:
- /srv/lsio/ldap-auth/config:/config
environment:
PUID: '1000'
PGID: '1000'
TZ: Etc/UTC
FERNETKEY: ''
CERTFILE: ''
KEYFILE: ''
restart: unless-stopped
Save this file as ldap-auth-stack.yml, then from a manager node, run docker stack deploy -c ldap-auth-stack.yml ldap-auth
version: '3.8'
services:
ldap-auth:
image: linuxserver/ldap-auth:latest
ports:
- 8888:8888/tcp
- 9000:9000/tcp
volumes:
- /srv/lsio/ldap-auth/config:/config
environment:
PUID: '1000'
PGID: '1000'
TZ: Etc/UTC
FERNETKEY: ''
CERTFILE: ''
KEYFILE: ''
deploy:
restart_policy:
condition: any
Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a
persistent volume claim, and ports are exposed via a LoadBalancer service.
ldap-auth-deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: ldap-auth
labels:
app: ldap-auth
spec:
replicas: 1
selector:
matchLabels:
app: ldap-auth
template:
metadata:
labels:
app: ldap-auth
spec:
containers:
- name: ldap-auth
image: linuxserver/ldap-auth:latest
env:
- name: PUID
value: '1000'
- name: PGID
value: '1000'
- name: TZ
value: Etc/UTC
- name: FERNETKEY
value: ''
- name: CERTFILE
value: ''
- name: KEYFILE
value: ''
ports:
- containerPort: 8888
protocol: TCP
- containerPort: 9000
protocol: TCP
volumeMounts:
- name: ldap-auth-data-0
mountPath: /config
volumes:
- name: ldap-auth-data-0
hostPath:
path: /srv/lsio/ldap-auth/config
ldap-auth-service.yaml
apiVersion: v1
kind: Service
metadata:
name: ldap-auth
spec:
type: LoadBalancer
selector:
app: ldap-auth
ports:
- name: 8888-tcp
port: 8888
targetPort: 8888
protocol: TCP
- name: 9000-tcp
port: 9000
targetPort: 9000
protocol: TCP
Save this file as ~/.config/containers/systemd/ldap-auth.container
[Unit]
Description=Ldap-auth
[Container]
Image=linuxserver/ldap-auth:latest
ContainerName=ldap-auth
PublishPort=8888:8888/tcp
PublishPort=9000:9000/tcp
Environment=PUID=1000
Environment=PGID=1000
Environment=TZ=Etc/UTC
Environment=FERNETKEY=
Environment=CERTFILE=
Environment=KEYFILE=
Volume=/srv/lsio/ldap-auth/config:/config
[Service]
Restart=always
[Install]
WantedBy=default.targetThen reload systemd and start the service:
systemctl --user daemon-reload
systemctl --user start ldap-authFor a system-wide service, use /etc/containers/systemd/ and drop --user.
For more installation options, see the Documentation in our GitHub repo
For app-specific guidance, check Ldap-auth's own repo at nginxinc/nginx-ldap-auth

The LinuxServer.io team brings you another container release featuring:
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
linuxserver/ldap-auth
Ldap-auth software is for authenticating users who request protected resources from servers proxied by nginx. It includes a daemon (ldap-auth) that communicates with an authentication server, and a webserver daemon that generates an authentication cookie based on the user’s credentials. The daemons are written in Python for use with a Lightweight Directory Access Protocol (LDAP) authentication server (OpenLDAP or Microsoft Windows Active Directory 2003 and 2012).

Supported Architectures
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.Simply pulling
lscr.io/linuxserver/ldap-auth:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.The architectures supported by this image are:
| Architecture | Available | Tag | | :----: | :----: | ---- | | x86-64 | ✅ | amd64-\
Application Setup
- This container itself does not have any settings and it relies on the pertinent information passed through in http headers of incoming requests. Make sure that your webserver is set up with the right config.
- Here's a sample config: nginx-ldap-auth.conf.
- Unlike the upstream project, this image encodes the cookie information with fernet, using a randomly generated key during container creation (or optionally user defined).
- Also unlike the upstream project, this image serves the login page at
/ldaplogin(as well as/login) to prevent clashes with reverse proxied apps that may also use/loginfor their internal auth.
Read-Only Operation
This image can be run with a read-only container filesystem. For details please read the docs.Non-Root Operation
This image can be run with a non-root user. For details please read the docs.Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.>!NOTE >Unless a parameter is flagged as 'optional', it is mandatory and a value must be provided.
docker-compose (recommended, click here for more info)
---
services:
ldap-auth:
image: lscr.io/linuxserver/ldap-auth:latest
container_name: ldap-auth
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- FERNETKEY= #optional
- CERTFILE= #optional
- KEYFILE= #optional
ports:
- 8888:8888
- 9000:9000
restart: unless-stoppeddocker cli (click here for more info)
docker run -d \
--name=ldap-auth \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-e FERNETKEY= `#optional` \
-e CERTFILE= `#optional` \
-e KEYFILE= `#optional` \
-p 8888:8888 \
-p 9000:9000 \
--restart unless-stopped \
lscr.io/linuxserver/ldap-auth:latestParameters
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate<external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.| Parameter | Function | | :----: | --- | |
-p 8888:8888 | the port for ldap auth daemon |
| -p 9000:9000 | the port for ldap login page |
| -e PUID=1000 | for UserID - see below for explanation |
| -e PGID=1000 | for GroupID - see below for explanation |
| -e TZ=Etc/UTC | specify a timezone to use, see this list. |
| -e FERNETKEY= | Optionally define a custom valid fernet key (only needed if container is frequently recreated, or if using multi-node setups, invalidating previous authentications) |
| -e CERTFILE= | Optionally point this to a certificate file to enable HTTP over SSL (HTTPS) for the ldap auth daemon |
| -e KEYFILE= | Optionally point this to the private key file, matching the certificate file referred to in CERTFILE |
| --read-only=true | Run container with a read-only filesystem. Please read the docs. |
| --user=1000:1000 | Run container with a non-root user. Please read the docs. |Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prependFILE__.As an example:
-e FILE__MYVAR=/run/secrets/mysecretvariableWill set the environment variable
MYVAR based on the contents of the /run/secrets/mysecretvariable file.Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional-e UMASK=022 setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.User / Group Identifiers
When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance
PUID=1000 and PGID=1000, to find yours use id your_user as below:id your_userExample output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)Docker Mods
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Support Info
- Shell access whilst the container is running:
```bash
docker exec -it ldap-auth /bin/bash
```- To monitor the logs of the container in realtime:
```bash
docker logs -f ldap-auth
```- Container version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' ldap-auth
```- Image version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ldap-auth:latest
```Updating Info
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.Below are the instructions for updating containers:
Via Docker Compose
- Update images:
* All images:
```bash
docker-compose pull
```
* Single image:
```bash
docker-compose pull ldap-auth
```- Update containers:
* All containers:
```bash
docker-compose up -d
```
* Single container:
```bash
docker-compose up -d ldap-auth
```- You can also remove the old dangling images:
```bash
docker image prune
```Via Docker Run
- Update the image:
```bash
docker pull lscr.io/linuxserver/ldap-auth:latest
```- Stop the running container:
```bash
docker stop ldap-auth
```- Delete the container:
```bash
docker rm ldap-auth
```- Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) - You can also remove the old dangling images:
```bash
docker image prune
```Image Update Notifications - Diun (Docker Image Update Notifier)
>!TIP >We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.Building locally
If you want to make local modifications to these images for development purposes or just to customize the logic:git clone https://github.com/linuxserver/docker-ldap-auth.git
cd docker-ldap-auth
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/ldap-auth:latest .The ARM variants can be built on x8664 hardware and vice versa using
lscr.io/linuxserver/qemu-staticdocker run --rm --privileged lscr.io/linuxserver/qemu-static --resetOnce registered you can define the dockerfile to use with
-f Dockerfile.aarch64.Versions
- 17.07.26: - Rebase to Alpine 3.24.
- 25.12.24: - Add
legacy-cgi. Fix fernet key storage. - 22.12.24: - Rebase to Alpine 3.21. Add support for read-only and non-root.
- 30.06.24: - Rebase to Alpine 3.20.
- 23.12.23: - Rebase to Alpine 3.19.
- 20.06.23: - Sync upstream changes, including the ability to disable referrals with
X-Ldap-DisableReferrals. - 25.05.23: - Rebase to Alpine 3.18, deprecate armhf.
- 30.12.22: - Rebase to alpine 3.17.
- 19.09.22: - Rebase to alpine 3.15.
- 14.05.21: - Add linuxserver wheel index.
- 12.02.21: - Clean up cargo/rust cache.
- 10.02.21: - Rebasing to alpine 3.13.
- 08.09.20: - Set form action correctly.
- 30.07.20: - Fix bug related to unset optional
CERTFILEandKEYFILEvars. - 27.07.20: - Add support for HTTP over SSL (HTTPS).
- 21.07.20: - Add support for optional user defined fernet key.
- 02.06.20: - Rebasing to alpine 3.12, serve login page at
/ldaploginas well as/login, to prevent clashes with reverese proxied apps. - 17.05.20: - Add support for self-signed CA certs.
- 20.02.20: - Switch to python3.
- 19.12.19: - Rebasing to alpine 3.11.
- 01.07.19: - Fall back to base64 encoding when basic http auth is used.
- 28.06.19: - Rebasing to alpine 3.10.
- 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
- 22.02.19: - Rebasing to alpine 3.9.
- 18.09.18: - Update pip
- 14.09.18: - Add TZ parameter, remove unnecessary PUID/PGID params
- 11.08.18: - Initial release.
Serve Ldap-auth on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying ldap-auth.example.com to http://Ldap-auth:9000
Add this to your Caddyfile
ldap-auth.example.com {
reverse_proxy http://Ldap-auth:9000
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs Ldap-auth - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:8888 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8888 - Stop the other service, or pick a different host port. In
8888:8888only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:8888. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, Ldap-auth can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8888
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /srv/lsio/ldap-auth/config - Or set the
PUIDandPGIDvariables (defaults 1000:1000) to match your own user, found withid $USER
Image won't pull
Test the pull directly on the host: docker pull linuxserver/ldap-auth:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect Ldap-auth --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Required settings are blank
FERNETKEY, CERTFILE, KEYFILE have no default value, and Ldap-auth may crash or misbehave if left empty.
- Fill them in on the deploy screen before hitting deploy.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on nginxinc/nginx-ldap-auth
- Template not working: Open an issue on technorabilia/portainer-templates
- This website not working: Open an issue on lissy93/portainer-templates