-
LDAP WebGUI v1.35.0
StableAll checks were successfulTests / Scope (push) Successful in 1sTests / pytest (newest CPython, warning only) (push) Has been skippedTests / 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 30sTests / pytest (Python 3.13) (push) Successful in 22m16sTests / pytest (Python 3.14) (push) Successful in 23m51sTests / Publish release (push) Successful in 3sreleased this
2026-11-12 00:20:18 +01:00 | 2 commits to main since this releaseUpgrade notes
- One manual step for a directory with more than 500 entries in an
area (users, groups or sudo rules) whose bind account has no
olcLimitsline yet. slapd counts its size limit over the whole paged
search, so the WebGUI's bind account needs
olcLimits: dn.exact="<bind DN>" size.prtotal=unlimitedon the data
database. On the directory host an update at a terminal shows the line,
asks and adds it; the web update never writes to slapd and names
sudo ldap-webgui-update --ldap-limitsinstead. With slapd on another
host, the update to this release shows the readyldapmodifyonce.
An existingsize=unlimitedline (recommended since 1.32) stays valid
— nothing to do; keep it if you may go back below this release.
Smaller directories need nothing.docs/ldap-acl-setup.md→ Size
limit for the bind account. - The nginx vhost is unchanged in this release.
Added
- Areas of any size: every directory read — the user, group and
sudo-rule lists, the Machines page, a group's primary members, the
search for the next free uidNumber/gidNumber — runs as a paged search
(pages of 250) and returns the whole area; filters always search all of
it. Where slapd still cuts the result, the page fails with the exact
olcLimitsline for the configured bind DN instead of showing a
partial list, and automatic IDs are refused, as before. update.sh --ldap-limitsand a check after every update: is this
host the directory host (slapd active here, a database for
ldap.base_dn,ldap.hostone of this host's addresses)? Then the
bind account's line is in place, or offered. A broaderolcLimits
value in front of it (users,*, a subtree …) wins over it in
slapd — reported with the list in the right order, never reordered
automatically. A failed check is a warning, never a failed update.bootstrap-ldap.shsets the line on the directory it builds; an
existing value for the bind account is left as it is.
Changed
- The CSV export reads the users once instead of once per 200 rows.
docs/ldap-acl-setup.md:size.prtotal=unlimitedis the recommended
line; the pitfallssize.hardalone,size.pr, root overldapi:///
(not exempt) and the order ofolcLimitsvalues.
Fixed
- Detail pages no longer report a failed read as "not found". A user,
group or sudo rule whose read hits a directory limit (or fails
otherwise) now shows "Could not read …" with the cause; "not found"
only when the entry really does not exist. Same for the sudo toggle on
the user page.
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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- One manual step for a directory with more than 500 entries in an