• v1.24.2 4c8d50e215

    LDAP WebGUI v1.24.2
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 2m30s
    Tests / pytest (Python 3.12) (push) Successful in 2m39s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 17s
    Release / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-11-01 23:02:14 +01:00 | 20 commits to main since this release

    Fixed

    • A passed preflight offers Install without Check for Updates
      first.
      Run preflight now refreshes the update check the way the
      button does and asks for the release it announces. Before, a stale
      cache sent an unpinned preflight that passed for the newer release,
      yet Install never appeared, because the card still knew of no newer
      release. If the forge is unreachable the preflight runs as before; if
      this host already runs the latest release the reply says so.
    • htmx sends the CSRF header the server reads. The page set
      X-CSRFToken, the server checks X-CSRF-Token; every form htmx posts
      also carries the hidden token field, so nothing failed — but a request
      without that field would have been refused. Now both say
      X-CSRF-Token.

    Upgrade notes

    • No nginx/ldap-webgui.conf change.

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads
  • v1.24.1 a4e33df942

    LDAP WebGUI v1.24.1
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 2m42s
    Release / Publish release (push) Successful in 3s
    Tests / pytest (Python 3.12) (push) Successful in 3m34s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 18s
    Stable

    Lyra released this 2026-11-01 21:33:01 +01:00 | 21 commits to main since this release

    Added

    • A banner while the host is unrestricted. Every page shows a warning
      at the top, to both roles and not dismissible, while nginx admits
      every network (no access include in the vhost, no deny all; after
      it, or allow all;); it links to Settings → Access. An unknown
      state shows no banner — it stays on the card.

    Changed

    • One list of documents. Documentation (/docs/) and the
      Documentation card in Settings render the same cards — title,
      one-line description, grouped into Setup & operation, Directory &
      access
      and Schemas & LDIF. The Settings card had fallen behind and
      was missing Isolated Hosts and the sudo schema LDIF; a document
      without an entry still appears on /docs/, titled by its heading.

    Upgrade notes

    • No nginx/ldap-webgui.conf change. A host updated to 1.24.0 without
      the access include now shows the banner until the include is in place
      (1.24.0 → Upgrade notes).

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads
  • v1.24.0 eb10d684d8

    LDAP WebGUI v1.24.0
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 2m36s
    Tests / pytest (Python 3.12) (push) Successful in 2m41s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 2m41s
    Release / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-11-01 19:50:27 +01:00 | 22 commits to main since this release

    Added

    • Who may reach the WebGUI. nginx now admits loopback plus the hosts
      and networks in /etc/nginx/ldap-webgui-access.conf, and nothing else;
      /health additionally admits the monitoring hosts in
      /etc/nginx/ldap-webgui-monitoring.conf. The guided setup asks for both
      (Access, suggesting the address of your SSH session); install.sh
      takes --allow LIST and --allow-monitoring LIST (IPv4/IPv6, CIDR —
      a network with host bits set is refused with the corrected form).
      any writes an unrestricted list and needs a second, explicit
      confirmation (typed yes, access_any_keep=yes, or --confirm-any).
      Loopback is always in the list — the health checks of the setup and of
      every update go through https://localhost/health.
    • Settings → Access shows both lists read-only, whether the host is
      restricted, unrestricted or in an unknown state, and which entry admits
      your own address.
    • README → Operating recommendation: admin network or VPN only, never
      internet-facing; ideally from a jump host, at least from a browser
      profile that is not the everyday one.

    Changed

    • install.sh stops when nginx -t fails after it wrote an access
      file
      , and puts the previous file back — before, a failing nginx -t
      was only a warning. A re-install that keeps both files still warns.
    • install.sh without --allow keeps an existing access file; where
      there is none it writes loopback only and says how to open it.
    • The vhost no longer has an ACME /.well-known/acme-challenge/
      exception on port 80, and no longer recommends certbot — certificates
      come from your own CA.
    • Port 80's redirect and /robots.txt answer only allowed hosts. A
      plain return runs before nginx's allow/deny; both now go through
      try_files to a named location, which is reached only after the
      access check. Carry this over with the include lines.

    Fixed

    • An existing directory's CA certificate is trusted by the system.
      setup.sh (directory existing) checked the CA as root, then wrote its
      path into config.yaml unchanged — a CA under /root passed the check,
      but the service (ldapwebgui, ProtectHome=true) could not read it,
      /health answered 503 and the setup stopped at start. Unless the
      system already trusts it (same SHA-256 fingerprint in
      /etc/ssl/certs/ca-certificates.crt, which ldap.tls.ca_cert then
      names), the setup copies it to
      /usr/local/share/ca-certificates/ldap-webgui-ca.crt, runs
      update-ca-certificates and names that file. It stays trusted if the
      WebGUI is removed: delete the file and run
      update-ca-certificates --fresh to undo.
    • setup.sh says why the WebGUI is not healthy. When /health does
      not answer 200 with the new version, the error now shows the last
      answer — the HTTP status and the start of the body, e.g. HTTP 503: {"ldap": "unreachable", ...} — instead of only pointing at the journal
      and app.log, which do not record a failed LDAP connection.

    Upgrade notes

    • nginx/ldap-webgui.conf changed. update.sh never installs the
      vhost, so an updated host stays unrestricted until you change it by
      hand; the update's nginx drift check says so. Order matters — create
      the files first, or nginx -t fails on the missing includes:

      printf 'allow 127.0.0.1;\nallow ::1;\nallow 192.168.10.0/24;\n' \
          > /etc/nginx/ldap-webgui-access.conf        # your admin hosts/networks
      printf '# monitoring hosts, /health only\n' \
          > /etc/nginx/ldap-webgui-monitoring.conf
      

      Then add include /etc/nginx/ldap-webgui-access.conf; and deny all;
      to both server blocks, and to location = /health the two includes
      (access, then monitoring) followed by deny all; — exactly as in the
      shipped nginx/ldap-webgui.conf. nginx -t && systemctl reload nginx.
      Keep 127.0.0.1 and ::1: without them every update rolls back.

    • Re-running install.sh on such a host copies the new vhost and,
      without --allow, writes loopback only — pass --allow with your admin
      hosts.

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads
  • v1.23.0 57ddf5c536

    LDAP WebGUI v1.23.0
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 2m0s
    Tests / pytest (Python 3.12) (push) Successful in 2m1s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 16s
    Release / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-11-01 15:52:14 +01:00 | 23 commits to main since this release

    Changed

    • Vendored Alpine 3.17.2 → 3.17.5 (@alpinejs/csp, three upstream
      patch releases). The new filename alpine-3.17.5-csp.js is a new URL,
      so a copy cached under the immutable header cannot outlive it. The
      file is the npm tarball's dist/cdn.min.js, checked against its
      dist.integrity. update.sh installs it like any other vendored file.
      No change to the nginx vhost.

    Documentation

    • docs/isolated-hosts.md — running the WebGUI in an isolated
      network.
      What the host reaches out to and when (forge, PyPI, the
      Debian mirror), and three ways to work without egress: a firewall rule
      for the update window, a wheelhouse, or archive updates without the
      forge. README's offline notes (still on Python 3.11, without platform
      flags) now point there.

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads
  • v1.22.1 72ce18b0bd

    LDAP WebGUI v1.22.1
    All checks were successful
    Tests / pytest (Python 3.12) (push) Successful in 2m1s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 16s
    Tests / pytest (Python 3.11) (push) Successful in 1m57s
    Release / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-11-01 13:01:28 +01:00 | 25 commits to main since this release

    Security

    • Python dependencies with known advisories updated (pip-audit
      against requirements.txt and requirements-dev.txt is clean again):

      Package Was Now Advisories fixed
      Pillow (QR codes for 2FA) 11.1.0 13.0.0 69
      cryptography (Fernet in the CSV import) 44.0.2 50.0.2 10
      Werkzeug 3.1.3 3.1.9 7
      Flask 3.1.0 3.1.3 4
      pytest (development only) 8.3.4 9.2.0 2

      cryptography 50 pulls in cffi 2.x. Nothing in the application had
      to change; Python 3.11 and newer as before.

    Fixed

    • "Reload the page to use it" no longer stays forever. The hint
      belongs to a Settings page that was open during the install and learnt
      the result by polling; a page loaded afterwards already runs the new
      version and now only says Installed vX.Y.Z.

    Upgrade notes

    • New wheels for hosts without PyPI egress. The update installs the
      new pins through pip; a host that cannot reach PyPI fails the preflight
      at Check Python dependencies until its wheelhouse has them. On a
      machine with access, from this release's requirements.txt (Debian 13
      is CPython 3.13 — check python3 -V on the host):

      pip download --only-binary=:all: --python-version 3.13 --implementation cp \
          --platform manylinux_2_28_x86_64 --platform manylinux_2_17_x86_64 \
          -r requirements.txt -d ldap-webgui-wheels
      

      Copy the files into the host's wheelhouse (the directory its
      /etc/pip.conf names in find-links), then run the preflight.

    • No nginx/ldap-webgui.conf change.

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads
  • v1.22.0 29df0a41c1

    LDAP WebGUI v1.22.0
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 1m59s
    Tests / pytest (Python 3.12) (push) Successful in 2m0s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 16s
    Release / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-11-01 11:53:54 +01:00 | 26 commits to main since this release

    Added

    • A guided install from one command. On a bare Debian 13 host, as
      root: bash -c "$(curl -fsSL https://git.dynnet.de/DravenTec/ldap-webgui/raw/branch/main/get_ldap-webgui.sh)"
      (or with wget -qO-). get_ldap-webgui.sh installs git and curl,
      clones the newest release (a tag) to /usr/local/src/ldap-webgui and
      starts its setup.sh. The setup asks first — a new directory on this
      host (through bootstrap-ldap.sh) or an existing one — shows a summary
      without passwords, and acts only after Proceed? [y/N]. It ends with a
      running WebGUI, the update check pointed at the release source, and,
      if wanted, Settings → Software Update enabled. Log:
      /var/log/ldap-webgui-setup.log. --answers FILE runs it unattended
      (the admin password of a new directory is still prompted).
    • An existing directory is checked read-only before anything is
      written: TLS with the given CA, the bind, every base, the admin group
      and its members, the sudo schema. Write access is not tested — the bind
      account needs it on users, groups and sudo rules
      (docs/ldap-acl-setup.md).
    • Hosts without PyPI access: the setup notices before it changes
      anything and prints how to stage the Python packages. With
      --wheelhouse DIR it writes a permanent /etc/pip.conf (no-index,
      find-links) so later updates install from the same directory; an
      existing /etc/pip.conf with find-links is used as it is.
    • bootstrap-ldap.sh --write-config PATH --config-block FILE applies a
      given block instead of the bootstrap's own.

    Fixed

    • install.sh and update.sh make every installed file group-readable
      for the service, not only *.py. Under a root umask of 077, templates
      and VERSION stayed 0600: the service started, but pages failed and
      /health reported version "unknown".
    • sudo is now in debian-packages.txt. install.sh and update.sh
      run checks as the service user with sudo -u, and a minimal Debian 13
      has no sudo. An installed host without it: apt-get install sudo.

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads
  • v1.21.0 a5c155dda3

    LDAP WebGUI v1.21.0
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 1m16s
    Tests / pytest (Python 3.12) (push) Successful in 1m17s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh) (push) Successful in 15s
    Release / Publish release (push) Successful in 2s
    Stable

    Lyra released this 2026-10-31 23:33:30 +01:00 | 27 commits to main since this release

    Added

    • What's new, before an install. Install vX.Y.Z first opens that
      release's notes in the dialog — upgrade notes included — and
      Continue leads to the confirmation with Install; Back returns to
      the notes. The notes come from the same request the update check
      already makes and are cached as Markdown. Over 32 KB, or for a version
      other than the one on offer, the dialog shows the link to the release
      page instead, as in v1.20.2.

    Fixed

    • Last preflight no longer reads "failed" after a preflight on a host
      that was already up to date — it says "passed — already on the latest
      release".

    Security

    • Release notes are text from the network and are rendered as such:
      raw HTML stays text, images are dropped (their alt text stays), and
      only https:// links survive — every other link, including
      javascript:, data:, http:, relative and # targets, becomes its
      text. Links that remain open in a new tab with
      rel="noopener noreferrer". The check runs on the element tree, not
      on the HTML string, and does not rely on the vhost's CSP. /docs/
      renders the project's own documents unchanged.

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads
  • v1.20.2 97d3170cd3

    LDAP WebGUI v1.20.2
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 1m9s
    Tests / pytest (Python 3.12) (push) Successful in 1m10s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh) (push) Successful in 15s
    Release / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-10-31 01:10:48 +01:00 | 28 commits to main since this release

    Added

    • Release notes before an install. The Install vX.Y.Z dialog links
      the release notes of exactly that version — the upgrade notes list the
      manual steps. Check for Updates links them when up to date as well.

    Fixed

    • The Check for Updates text no longer reads "Switched off until that
      section is configured" on a host where it is configured and working.
    • A SyntaxWarning from a docstring in the login redirect check
      (a backslash in a non-raw string) — visible on a fresh install without
      bytecode cache, an error in a future Python.
    • README: the opening no longer claims no LDIF is ever written by hand —
      the initial setup adapts one template once (none with
      bootstrap-ldap.sh).

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads
  • v1.20.1 387297ef7b

    LDAP WebGUI v1.20.1
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 1m18s
    Tests / pytest (Python 3.12) (push) Successful in 1m17s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh) (push) Successful in 16s
    Release / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-10-30 23:57:08 +01:00 | 30 commits to main since this release

    v1.20.0's code, re-published as the first release of a clean release
    repository: one commit per release, nothing but what ships. The
    development history lives in a separate repository. No code change.

    Changed

    • The release repository starts over at this release. Its main
      does not descend from the main of v1.20.0 and earlier, and the older
      tags and releases are not carried over.
    • Comments and documentation no longer point at development records
      that do not ship; where a pointer carried a reason, the reason is now
      written out in place.
    • The release workflow publishes a release only in the release
      repository; anywhere else a version tag is a marker and nothing is
      published.
    • /docs/ serves every operator document in docs/ — the repository
      carries no development records there any more.

    Upgrade notes

    • Every host that updates from a git clone has to re-clone once. The
      new main does not descend from the old one, so
      ldap-webgui-update --from-release (and the web update) refuses at
      step source with exit 1 and changes nothing. As root: move the old
      clone at /usr/local/src/ldap-webgui aside, git clone the release
      repository to the same path, re-create the clone-local credential
      helper if the old clone had one, chown -R root:root the new clone,
      then sudo ldap-webgui-update --from-release —
      docs/settings.md → Re-cloning the update clone.
    • For a private release repository, the access token in
      /etc/ldap-webgui/environment must be one that can read the new
      repository — a token bound to a single repository may have to be
      replaced before the re-clone.
    • An archive install is not affected; update it as before.
    • No nginx change.

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads