• v1.25.2 3e5669d10e

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

    Lyra released this 2026-11-02 02:05:59 +01:00 | 17 commits to main since this release

    Fixed

    • Settings → Save and Reload Configuration reach every worker. Only
      the worker that handled the request used the new values; the others
      kept the old password policy, sudo group, ID ranges and lockout
      thresholds until a restart, while the page said the change was active.
      Every worker now notices a changed config.yaml on its next request —
      a hand edit too. A file that does not parse keeps the running
      configuration, and the Reload button now says so instead of reporting
      success.

    • Saving settings can no longer leave a truncated config.yaml. The
      file used to be emptied before the new content was written, so a crash
      or a full disk in that moment cut off the secret key and the bind
      password, and the service did not start again. The new content is now
      complete before the file is touched (replaced atomically where the
      directory allows it), with mode and owner kept. Two admins saving at
      the same moment no longer lose one of the saves.

    • Log level and timezone from the settings form apply without a
      restart.
      The log level only took effect at the next start, and
      app.timezone had no effect at all — log timestamps now use it. An
      unknown timezone name is refused in the form.

    • CSV export now writes the title and description columns — they
      were always empty. An attribute with several values is written one
      value per line instead of as a Python list (['a', 'b']).

    • CSV export defuses cells a spreadsheet would run as a formula
      (starting with =, +, -, @, tab or carriage return) by
      prefixing a single quote; the import takes exactly that quote off
      again, so an exported file re-imports unchanged.

    • CSV export of more than 200 users fails with an error when a later
      page of the user list cannot be read, instead of silently producing a
      truncated file.

    • User page: a description with several values is shown as one field
      per value and saved as separate values. It used to appear as a Python
      list and was written back as that one corrupted value on any save.

    • Group page: a description with several values is shown as one
      field per value and saved as separate values, as on the user page —
      it used to appear as a Python list and collapse into one value on save.
      Only the values that changed are removed or added, so a description
      someone else changed meanwhile is reported instead of overwritten. The
      group list and a user's group memberships show several values joined
      instead of as a list.

    • User page: saving the description no longer rewrites the whole
      attribute. Only the visible values that changed are removed or added,
      so a two-factor enrolment completed at the same moment is never wiped,
      and a description someone else changed meanwhile is reported instead of
      overwritten.

    • CSV import: when an account was left in the directory although its
      row failed (the password could not be set and the rollback failed, or
      the connection broke after the add was sent), the next row no longer
      gets the same uidNumber.

    • install.sh re-run (e.g. --allow to change the access list) no
      longer overwrites an existing nginx vhost: one that includes the access
      list is kept as it is (server_name, certificate paths and local edits
      stay), and the installer prints how to compare it with the shipped
      template. Only a vhost without the access include is replaced, and its
      previous content is kept first as
      /etc/nginx/sites-available/ldap-webgui.pre-install-<timestamp>
      (root only).

    • install.sh with a failing nginx -t undoes everything it wrote to
      nginx in that run — the include files, the vhost, the site link, and
      the default site it disabled — instead of leaving an enabled vhost that
      includes deleted files. The rest of the installation (service, log
      rotation, update command) still happens; the summary says INCOMPLETE
      and the run exits 1. With --no-ssl it says the certificate must be in
      place first.

    • Settings → Access no longer reports restricted when nginx does not
      enforce the list everywhere: access rules below the server level (a
      nested location, if, limit_except), /health rules other than the
      shipped ones, or a plain-HTTP server block that serves the application
      instead of only redirecting now show unknown with the reason.

    • Settings → Access reads the other files the vhost includes
      (include proxy_params;, include snippets/ssl-params.conf;) instead
      of giving up on them. A relative path is looked up under /etc/nginx,
      as nginx does. A file without access rules, includes, location or
      server blocks keeps the state restricted; a pattern
      (snippets/*.conf), a missing or unreadable file, or one with such
      directives shows unknown and names the file and line. The page banner
      notices a change to an included file too.

    • update.sh never prunes the snapshot it has just taken. With the
      clock set back since earlier updates (NTP correction, timezone change)
      the new snapshot could sort as the oldest and be deleted at once, so a
      later failure could not roll back.

    • manage.py disable-2fa writes TOTP_DISABLED to the security log
      and ends the account's sessions only when two-factor authentication was
      actually removed, not for an account that never had it. A 2FA lockout
      is cleared either way.

    • Log rotation of /var/log/ldap-webgui runs as the service user
      (su ldapwebgui ldapwebgui in /etc/logrotate.d/ldap-webgui) instead
      of as root in a directory that user owns. The reload after rotation
      still runs as root.

    • Group page → Add Member clears the field and keeps the focus in it
      after a successful add again. The browser's security policy blocked
      that step, so the uid stayed in the box and pressing Enter a second
      time posted it again.

    • Group page → Add Member with a uid the server refuses (empty, or
      characters a uid cannot have) shows the error above the member list.
      It used to drop a second copy of the whole page into the list, which
      stayed broken until a reload. The outcome of adding or removing a
      member is now shown right there instead of as a message on the next
      page; when the group cannot be read back, the page reloads and says
      why.

    Upgrade notes

    • Log rotation: update.sh does not touch
      /etc/logrotate.d/ldap-webgui — only install.sh writes it. On an
      existing host, add the su line by hand (as root):
      sed -i '1a\ su ldapwebgui ldapwebgui' /etc/logrotate.d/ldap-webgui,
      then check it with logrotate -d /etc/logrotate.d/ldap-webgui.
    • install.sh now keeps an existing vhost that includes the access
      list. To pick up a newer template on such a host, compare and merge by
      hand: diff -u /opt/ldap-webgui/nginx/ldap-webgui.conf /etc/nginx/sites-available/ldap-webgui.
    • Log timestamps follow app.timezone. It is "UTC" in the example
      config, so on a host running in local time the timestamps in app.log
      and security.log move to UTC after the update. Set
      app.timezone (Settings → Editable Settings) to keep local time, e.g.
      Europe/Berlin.

    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