• v1.36.0 a0b81bcdf3

    LDAP WebGUI v1.36.0
    All checks were successful
    Tests / Scope (push) Successful in 1s
    Tests / pytest (newest CPython, warning only) (push) Has been skipped
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh, config-backup.sh, certtool.sh, accesstool.sh) (push) Successful in 30s
    Tests / pytest (Python 3.13) (push) Successful in 22m19s
    Tests / pytest (Python 3.14) (push) Successful in 24m2s
    Tests / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-11-12 21:02:53 +01:00 | 1 commits to main since this release

    Upgrade notes

    • One manual step, needed only for Machines → Register: the host
      register lives in ou=hosts and needs one ACL rule for the bind
      account. Neither the update nor the web update touches slapd; without
      the step the machines pages work as before and only Register is
      disabled, pointing to the guide. The update counts it under "One
      manual step is left", and the web update shows it in its status box.
      Procedure, check and way back:
      docs/upgrade-1.36.md. Directories built by bootstrap-ldap.sh from
      this release on carry the OU and the rule already.
    • ldap.all_hosts_group in config.yaml is ignored now (see
      Removed); remove the line at your convenience.
    • The nginx vhost is unchanged in this release.

    Added

    • Host register (Machines → Register): one device entry per host
      below ldap.hosts_base (default ou=hosts,<base DN>), the short name
      exactly as hostname prints it, case-sensitive, plus an optional
      description. A registered host's spelling is the reference: sudoHost
      values spelled differently are flagged against it, on the machines
      pages and on the sudo form. Invalid entries in the OU are listed and
      otherwise ignored.
    • Writes from the host page: register a host, edit its description,
      delete it (refused while a sudo rule still names it, exact-case
      confirmation), add a registered host to an existing sudo rule, remove
      a host from a rule (also an unregistered one — that is how a typo
      leaves a rule), and Create a sudo rule for this host with sudoHost
      prefilled. Each sudo-rule edit is one value, never a replace of the
      rule's hosts; security log HOST_CREATED / HOST_UPDATED / HOST_DELETED
      and SUDO_ROLE_UPDATED with host_added= / host_removed=.
    • New group names may carry upper case ([A-Za-z_][A-Za-z0-9._-],
      at most 32), with the hint that AllowGroups on the host takes the
      name exactly as spelled. User and service-account names stay lower
      case.
    • Host names up to 63 characters (one RFC 1123 label; was 58).
    • ldap.hosts_base (config.yaml only) and a read-only Hosts Base row
      on the Settings page.

    Changed

    • The host page shows sudo only: every sudo rule matching the host,
      resolved to people with the path per person (via %group, via user). Login is the host's AllowGroups in sshd_config and is not
      modelled; docs/machines.md explains how to keep login groups and
      sudo groups apart.
    • The host list comes from the register and the sudoHost values; the
      Machines card on a group page shows sudo only.
    • bootstrap-ldap.sh creates ou=hosts and its ACL rule {8} (eleven
      rules); a resumed run on a tree with the previous ten-rule set
      upgrades it. docs/ldap-acl-setup.md and docs/initial-admin.ldif
      follow.

    Removed

    • The per-host login view: the AllowGroups line, the login columns
      and the group card's "Opens login on" / "Logs in everywhere" lines.
    • login-<host> groups as a host source — such a group is an ordinary
      posixGroup and names no host any more.
    • ldap.all_hosts_group — ignored, with one warning in the log while
      config.yaml still sets it; the Settings page's All-Hosts Group
      row.

    Fixed

    • A concurrent description change on a group or user is reported
      ("changed by someone else in the meantime — nothing was saved")
      instead of a raw LDAP error.
    • Creating a group that already exists in another case
      (Web vs. web, or a race past the check) answers with the stored
      spelling, or a plain "already exists", instead of the LDAP result
      text.
    • The group-name hint on the create form promised 64 characters and
      mixed case while the server allowed 32, lower case; it now states the
      actual rule.
    • docs/initial-admin.ldif pointed to ACL rule {7} for
      ou=service-accounts; it is {9} with the new rule.
    • The host page and docs/machines.md said sss_cache -E makes a sudo
      change immediate on the host. It does for removals and narrowed rules,
      not for a rule that newly applies to a user or host — that one waits
      for SSSD's smart refresh or needs an emptied SSSD cache (the steps are
      in docs/machines.md); sss_cache is in sssd-tools.

    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