-
LDAP WebGUI v1.32.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.11) (push) Successful in 19m22sTests / pytest (Python 3.13) (push) Successful in 20m37sTests / Publish release (push) Successful in 4sreleased this
2026-11-06 20:29:37 +01:00 | 7 commits to main since this releaseAdded
- Machines — a read-only host register. A new Machines entry in
the navigation (after Sudo Rules, both roles) answers per host who
may log in over SSH and who has sudo there, derived from the directory
as it is: a host is every name asudoHostvalue gives (dotted values
by their first label, negated ones included) and every posixGroup
login-<host>. Nothing is stored, nothing is written to LDAP.
/machines/lists the hosts (server-side?q=filter) with their
source, the people inlogin-<host>, the rules naming them, a flag
when only FQDN values name a host, and an inconsistent spelling flag
listing the spellings found; above the table what applies everywhere,
below it the rules that may apply on every host./machines/<host>(any case) shows the line for that host's
sshd_configwith a copy button —AllowGroups login-<host>, or with
the all-hosts group in front — the people it lets in with the path
each came by (memberUidand primary group, service accounts marked),
the sudo rules that apply, are excluded by a negated value, match only
by FQDN or may apply, the people they resolve to one level deep, the
members of the sudo group, and the caveats: the WebGUI cannot see
sshd_configor the local sudoers, so every answer is labelled
if the host has the line. Guide:docs/machines.md. ldap.all_hosts_group(config.yaml, optional, empty by default):
the cn of a posixGroup whose members may log in on every host. When
set, it leads every host'sAllowGroupsline and its members are
listed on every host page; a cn that names no posixGroup with a
gidNumber gives a warning there. An invalid name is logged at startup
and treated as unset. Shown read-only under Settings → LDAP
Connection. Seedocs/settings.md.- A Machines card on every group page: "Opens login on " for
alogin-<host>group, "Logs in everywhere" for the all-hosts group,
the local-sudoers line forauth.sudo_group, and each sudo rule
naming the group (%<cn>,%#<gid>) with the hosts it names, linked
("every host except …" whenALLcomes with negated values). When the directory cannot be read for it, the
card says unavailable and the rest of the page is unchanged. - Annotated
sudoHostvalues on a sudo rule's page: each value with
its class (fqdn, opaque, wildcard, negated), host names linked
to their host page. ThesudoHostfield on the create and edit forms
carries a permanent hint that the spelling is case-sensitive — write
it exactly ashostnameprints it, because SSSD fetches a host's
rules by an exact-case match. A wildcard value (web*,db[0-9]) always shows
the hint that it applies only on clients with
ldap_sudo_include_regexp = trueinsssd.conf; it is allowed, never
refused. - Warnings after saving a sudo rule (create and edit), one flash per
finding: a wildcardsudoHost, and a host name whose spelling differs
only in case from another spelling of the same host in the directory —
only one of them can reach the host. Upper case alone never warns. The
save is never blocked or undone; an unchanged save still warns, and
when the directory cannot be read for the comparison only the wildcard
check runs.
Security
- An edit through an entry's link could write a different entry.
The uid/cn in the URL was cleaned by removing every character
outside the plain set and cutting at 64, and the page and every form
behind it then used the cleaned name:/users/a,bshowed and saved
the accountab, a 65-character uid its 64-character prefix, and
/sudo/fz-s,aliasthe rulefz-salias— edit, delete, password
reset, SSH keys, sudo grant, group members and sudo rules alike. A
URL whose uid or cn the cleaning would change is now refused with
400 before anything is read or written. Accounts, groups and sudo
rules with such names (a comma, a space, non-ASCII, more than 64
characters) are still listed but cannot be opened in the web GUI
until 1.32.1; manage them with the LDAP tools until then.
Fixed
- Lists were silently cut at the directory's size limit. ldap3 does
not raise onsizeLimitExceededortimeLimitExceeded, so a search
that hit slapd's limit (500 entries per search by default) returned
the first entries as if they were all of them: user, group and sudo
lists, the CSV import's uid set, the Machines page, the reference
scan before deleting an account and the scan for the next free
uidNumber/gidNumber all reported success on a partial answer. Every
search now checks the result code and fails visibly instead — the
page shows "The directory returned more entries than its size limit
allows (N) — raise olcSizeLimit/olcLimits for the bind account" (or
the time-limit equivalent), and an account delete or create is
refused. Existence checks (does this uid, group or sudo rule exist,
is the account in the sudo group) still accept a cut answer that
contains a match. - The dashboard counted a failed search as 0. With the size-limit
check above, a directory over slapd's limit made the user, group and
sudo lists fail — and the dashboard (and its Refresh) turned each
failure into 0, next to "Healthy". A count that cannot be read now
shows "—" with the reason as its tooltip; the group count depends on
the full user list (primary members), so a cut user search takes it
along. A sudoers base that does not exist is still 0 without an
error — the sudo schema is optional — and the sudo rules page says so
as a warning instead of the raw noSuchObject error. - One account with two
uidvalues broke every group page. The web
GUI never writes a seconduidorcn, but other tools can, and such
an entry came back with the value as a list: every group page failed
with an internal server error, the user list did too, and other
pages showed and linked the list's Python repr (the CSV export both
values in one cell). Users, groups and sudo
rules now always carry oneuid/cn— the first value; a user page
opened by its seconduidshows that one.
Upgrade notes
- No vhost change.
- Directories with more entries than slapd's size limit (500 per
search by default) inou=people, the groups or the sudoers subtree:
after the update the lists and the Machines page show "The directory
returned more entries than its size limit allows" instead of a
silently cut list, the dashboard shows "—" for the count, and
creating an account or group with
an automatically assigned ID is refused, until the limit is raised for
the WebGUI's bind DN — oneolcLimitsline, see
docs/ldap-acl-setup.md, Size limit for the bind account. Smaller
directories need nothing.
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
- Machines — a read-only host register. A new Machines entry in