Files
net-kingdom/sso-mfa/k8s/lldap
Bernd Worsch f2f07871eb fix(sso-mfa): commit T02–T06 fixes and workplan status updates
- authelia: users_filter uid→{username_attribute}, OIDC client secret
  moved from env var to inline bcrypt hash in configmap (4.38 limitation)
- authelia: remove unsupported CLIENTS_0_SECRET_FILE env var
- lldap: drop runAsNonRoot/runAsUser (image init requires root)
- verify-t02: keycloak→keycape NetworkPolicy check rename
- workplan: T02/T03/T05/T06 marked done with notes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-21 20:25:03 +00:00
..

T05a — LLDAP (Lightweight LDAP Directory)

LLDAP is the user and group directory for the net-kingdom SSO stack. It provides LDAP access to Authelia (credential validation) and KeyCape (user attribute lookup). The admin web UI is IP-restricted and never exposed publicly.

Prerequisites

  • T02 complete (namespaces and NetworkPolicies applied)
  • bootstrap/gen-secrets.sh run and secrets/lldap/secrets.env populated in KeePassXC
  • kubectl configured with cluster access

Apply order

# 1. Generate secrets (if not already done)
cd ../../bootstrap && ./gen-secrets.sh

# 2. Create K8s Secret
cd ../k8s/lldap
chmod +x create-secrets.sh
./create-secrets.sh

# 3. Apply manifests (order matters)
kubectl apply -f pvc.yaml
kubectl apply -f middleware.yaml
kubectl apply -f deployment.yaml
kubectl apply -f ingress.yaml

# 4. Wait for pod to be ready
kubectl rollout status deployment/lldap -n sso --timeout=120s

Post-deploy bootstrap

After the pod is Running, create the two required application groups via the web UI:

https://lldap.coulomb.social
Username: admin
Password: LLDAP_LDAP_USER_PASS (from KeePassXC → net-kingdom/LLDAP/admin)

Create groups:

  • net-kingdom-users — standard users
  • net-kingdom-admins — privileged users (enforce MFA step-up in KeyCape policies)

Ports

Port Protocol Access Purpose
3890 TCP (LDAP) Cluster-internal only Authelia + KeyCape LDAP bind
17170 TCP (HTTP) Traefik (IP-restricted) Admin web UI

The LDAP port is never exposed via Ingress. Only pods in the sso namespace with app.kubernetes.io/name=authelia or app.kubernetes.io/name=keycape labels are allowed to reach port 3890 (enforced by NetworkPolicy).

Secrets managed

Secret name Keys Purpose
lldap-secrets LLDAP_JWT_SECRET, LLDAP_LDAP_USER_PASS Pod environment variables

LLDAP_LDAP_USER_PASS is the admin bind password shared by Authelia and KeyCape. It must match the value used in authelia/create-secrets.sh and keycape/create-secrets.sh. All three read it from secrets/lldap/secrets.env.

Storage

lldap-data PVC (1 Gi, ReadWriteOnce) holds LLDAP's SQLite database.

Back this PVC up regularly — it contains all users and groups. If it is lost without a backup, all user accounts must be re-created and all applications must be re-enrolled in privacyIDEA.

Optional: switch to PostgreSQL by setting LLDAP_DATABASE_URL=postgresql://... env var in deployment.yaml and removing the PVC.

Verify

# Check pod status
kubectl get pod -n sso -l app.kubernetes.io/name=lldap

# Check LLDAP health via cluster-internal curl
kubectl run -n sso --rm -it ldap-test --image=busybox --restart=Never \
  -- wget -qO- http://lldap.sso.svc.cluster.local:17170/health

# Test LDAP bind (from another pod in the sso namespace)
# ldapwhoami -H ldap://lldap.sso.svc.cluster.local:3890 \
#   -D "uid=admin,ou=people,dc=netkingdom,dc=local" -w <LLDAP_LDAP_USER_PASS>