-
LDAP WebGUI v1.29.1
StableAll checks were successfulTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh, config-backup.sh, certtool.sh) (push) Successful in 28sRelease / pytest (Python 3.11) (push) Successful in 6m20sRelease / pytest (Python 3.13) (push) Successful in 6m29sRelease / Publish release (push) Successful in 4sTests / pytest (Python 3.11) (push) Successful in 18m21sTests / pytest (Python 3.13) (push) Successful in 19m38sTests / pytest (Python 3.15) (push) Successful in 20m51sreleased this
2026-11-04 23:34:10 +01:00 | 10 commits to main since this releaseAdded
- The host's IP addresses in the CSR (HTTPS, LDAP server and the
combined certificate alike), so the WebUI reached by its address is
covered too. The runner records the host's global addresses (private
and ULA included; no loopback, link-local or temporary IPv6 privacy
addresses). A host with a single IPv4 address gets it as an optional
default name. Otherwise the CSR form shows the addresses as a
checkbox group: the IPv4 address of the default route — and the one
your browser is using, if it is one of the host's — pre-ticked;
IPv6 addresses only after ticking Include IPv6 addresses, never
pre-ticked. Addresses are never required; the runner refuses one that
is not the host's. Runcerttool.sh --probe(install and update do)
to record them.
Changed
- CI tests Python 3.11 (oldest supported, Debian 12) and 3.13
(Debian 13) instead of 3.11 and 3.12; the newest CPython runs as well,
an early warning for the next Debian — it gates nothing. - The release workflow publishes only after the test suite passed on the
tagged tree (3.11 and 3.13); before, a release went out even when the
tests of the same tag failed.
Fixed
/2fa/disableon an account without 2FA no longer logs
TOTP_DISABLEDor signs out the account's other sessions; it now says
there was nothing to disable.bootstrap-ldap.sh's closing summary no longer tells you to install
the WebGUI on a host that already runs it; the next steps start with
writing the config (or only the restart when--write-configalready
ran).
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
- The host's IP addresses in the CSR (HTTPS, LDAP server and the
-
LDAP WebGUI v1.29.0
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 15m17sTests / pytest (Python 3.12) (push) Successful in 17m16sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh, config-backup.sh, certtool.sh) (push) Successful in 21sRelease / Publish release (push) Successful in 3sreleased this
2026-11-03 22:39:53 +01:00 | 11 commits to main since this releaseAdded
- One certificate for HTTPS and LDAP (Settings → Certificates, full
admins, password re-entry), offered when both single renewals are —
the renewal runner enabled and the directory this WebGUI uses is this
host's slapd. One CSR for both sides' names (ldap.hostas CN, RSA
3072) or one upload; every check of both sides runs before anything
is replaced, a CA change needs the same confirmation as for slapd.
Then both sides' files are swapped (*.prevkept), nginx is reloaded
and confirmed, slapd restarted and confirmed — any failure puts both
sides' previous files back. Security-log events carrytarget=both. - The CSR can be edited, for HTTPS, the LDAP server and the combined
certificate alike: an Advanced view (collapsed by default) lists the
names the CSR will carry, lets you leave out optional ones, add names,
choose the CN and set the subject fields O, OU, L, ST and C. Names
clients depend on cannot be left out. Without a recorded name list
(certtool.sh --probe) it offers extra names, CN and subject only. - A WebUI name field in the HTTPS and combined CSR and install
forms: the name browsers use, prefilled from the address you are
using, else the nginx site'sserver_name, else the host name.
Changed
- The HTTPS certificate must cover the WebUI name instead of
hostname -f; it is also the default CN. The host's own name becomes
an optional name of the CSR. A pending CSR made by 1.27/1.28 is still
checked againsthostname -f. - A host whose nginx and slapd share a certificate and/or key file —
refused by both single renewals since 1.28.0 — can now be renewed
with One certificate for HTTPS and LDAP; the shared files get
slapd's modes (root:openldap 0640key,root:root 0644cert). ldap-webgui-cert.service:TimeoutStartSecraised from 4 to
6 minutes — a combined install with a rollback reloads nginx and
restarts slapd twice.- Combined renewal with a CA change: the LDAP side's the new CA is not
in this host's system store replaces the HTTPS side's the CA is not
in this host's trust store instead of following it. - Settings reference: slapd should not reuse the installer's
self-signed HTTPS certificate — itslocalhostandIP:127.0.0.1
would have to be kept by every later LDAP renewal.
Fixed
- A CA change that removes the LDAP CA's trust-store entry now logs
CERT_TRUST_REMOVED, as the HTTPS entry's removal does. - A confirmed CA change no longer leaves
ldap-webgui-ca.crt.previn/usr/local/share/ca-certificates/; it
is kept only until the install is confirmed. /favicon.icoexists: the vhost has always pointed at
app/static/favicon.ico, but the file was never shipped, so every
browser logged a 404. The icon is the header logo.
Upgrade notes
- Nothing to do by hand. The nginx site is unchanged;
update.sh
installs the new service unit and reloads systemd. The renewal runner
stays off until enabled (systemctl enable --now ldap-webgui-cert.path, since 1.27.0).
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)
1 download
-
Source code (TAR.GZ)
0 downloads
- One certificate for HTTPS and LDAP (Settings → Certificates, full
-
LDAP WebGUI v1.28.0
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 6m24sTests / pytest (Python 3.12) (push) Successful in 6m40sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh, config-backup.sh, certtool.sh) (push) Successful in 20sRelease / Publish release (push) Successful in 3sreleased this
2026-11-03 00:15:08 +01:00 | 12 commits to main since this releaseAdded
- Renew the LDAP server's certificate from the web UI when the
WebGUI and slapd run on the same host (Settings → Certificates, full
admins, password re-entry). Offered only when the certificate the
directory serves is this host's slapd certificate; with a directory on
another host the card keeps showing its dates only. Same ways as for
HTTPS: the host makes an RSA 3072 key and a CSR (forldap.host, the
host's names and every name of the current certificate), or you upload
a certificate with its key. Before anything is replaced the
certificate must also coverldap.hostand every name the current
certificate covers, and chain to the CA the directory's clients
trust. Then the files are swapped (*.prevkept, the key
root:openldap 0640), slapd is restarted, and the new certificate
must be served, anldapsearchwith the CA must succeed and the
WebGUI's own/healthmust answer — otherwise the previous files go
back and slapd is restarted again. - A CA change is its own, confirmed step. A certificate that does not
chain to the directory's current CA — moving from the generated
self-signed certificate to your own CA is one — is installed only
after an explicit confirmation that every client (SSSD, a WebGUI on
another host) already trusts the new CA. The upload must end in the
new CA certificate; it replaces the directory's CA file together
with the certificate. A web request never adds a CA to the system
trust store — the generated CA's entry is removed, the new CA goes
there only by hand. A CA change needsldap.tls.ca_certset. - nginx and slapd must use their own files (
/etc/ssl/ldap-webgui/,
/etc/ldap/tls/); a certificate or key shared by both is refused. bootstrap-ldap.shadds the directory's CA to the system trust store
(/usr/local/share/ca-certificates/ldap-webgui-ca.crt).certtool.sh --proberecords this host's slapd certificate files
(from cn=config);install.sh,update.shandbootstrap-ldap.sh
run it.
Changed
- Security-log events
CERT_*carrytarget=nginx|slapd;
CERT_INSTALLEDfor slapd alsoca_change=yes|no.
Upgrade notes
- Nothing to do by hand. The renewal runner stays off until enabled
(systemctl enable --now ldap-webgui-cert.path, since 1.27.0); once
enabled it serves both certificates.
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
- Renew the LDAP server's certificate from the web UI when the
-
LDAP WebGUI v1.27.0
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 4m17sTests / pytest (Python 3.12) (push) Successful in 4m31sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh, config-backup.sh, certtool.sh) (push) Successful in 20sRelease / Publish release (push) Successful in 3sreleased this
2026-11-02 20:42:27 +01:00 | 13 commits to main since this releaseAdded
- Renew the HTTPS certificate from the web UI (Settings →
Certificates, full admins, password re-entry). Three ways: the host
makes a new key and a certificate signing request (the key never
leaves the host) and you upload the certificate your CA issued for
it; or you upload a certificate and its key issued elsewhere.
Before anything is replaced the certificate must match the key, be
valid now, cover the host's name and every requested name, be a
server certificate and chain to a trusted CA. Then the files are
swapped (the previous ones kept as*.prev), nginx is reloaded, and
the new certificate must actually be served — otherwise the previous
files go back. A root-owned runner does the work
(ldap-webgui-cert.path/.service); it is off until you enable
it. install.sh --tls-cert FILE --tls-key FILEuses an existing
certificate for nginx instead of generating one, with the same checks.
Changed
- New installs keep nginx's certificate in
/etc/ssl/ldap-webgui/
(cert.pem,key.pem) instead of/etc/ssl/certs/and
/etc/ssl/private/. Anything in/etc/ssl/certs/is hashed into
OpenSSL's trust directory by the nextupdate-ca-certificates, so a
certificate placed there becomes a trust anchor by accident. - A self-signed certificate generated by
install.shis added to the
system trust store explicitly
(/usr/local/share/ca-certificates/ldap-webgui-https.crt) and removed
again when a CA-issued certificate replaces it.
Upgrade notes
- The shipped nginx site changed (the certificate paths).
update.sh
never installs it; your site keeps working with its current paths.
Moving them out of/etc/ssl/certs/is recommended —
docs/upgrade-1.27.mdhas the steps, the check and the way back. - To renew from the web UI, enable the runner once:
systemctl enable --now ldap-webgui-cert.path(docs/upgrade-1.27.md).
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
- Renew the HTTPS certificate from the web UI (Settings →
-
LDAP WebGUI v1.26.0
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 2m53sTests / pytest (Python 3.12) (push) Successful in 2m55sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh, config-backup.sh) (push) Successful in 17sRelease / Publish release (push) Successful in 3sreleased this
2026-11-02 16:06:20 +01:00 | 14 commits to main since this releaseAdded
- Daily versioned backups of
config.yaml. A systemd timer
(ldap-webgui-config-backup.timer) copiesconfig.yamlonce a day to
/var/backups/ldap-webgui/config/(root only) — only when it changed
since the last copy. Copies younger than 30 days are kept, the newest
one always. A file that does not parse as YAML is never backed up and
nothing is pruned; the unit ends failed sosystemctl --failedand
monitoring see it. Restoring is by hand:docs/config-backup.md.
Background: the Settings save rewritesconfig.yamlin place, and a
power loss during exactly that write could still leave it damaged.
Upgrade notes
update.shinstalls the runner and both units and enables the timer
the first time it arrives; a timer you disable later stays disabled
across updates.install.shalways enables it. No manual step.
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
- Daily versioned backups of
-
LDAP WebGUI v1.25.4
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 2m43sTests / pytest (Python 3.12) (push) Successful in 2m48sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 18sRelease / Publish release (push) Successful in 3sreleased this
2026-11-02 14:13:30 +01:00 | 15 commits to main since this releaseSecurity
- Directory users can no longer read the TOTP secrets. The LDAP
WebGUI keeps a user's TOTP secret in thedescriptionattribute of
their entry — encoded, not encrypted. The recommended ACLs (and
bootstrap-ldap.sh) let every authenticated directory user read all
ofou=people,descriptionincluded, so anyone with a directory
account could read another user's secret and generate their codes.
A new rule lets only the WebGUI's bind account read and write
descriptionunderou=people.bootstrap-ldap.shsets it, checks it
in its verification, and recognises the previous rule set.
Changed
- License: LDAP WebGUI is licensed under the PolyForm Shield License
1.0.0 (LICENSE): free to use, change and run, also inside a company;
not to be offered as a competing product or service.
Fixed
- Documentation that contradicted the code: the TOTP secret is not
encrypted at rest; disabling 2FA asks for the password; 13 settings are
editable live, group DNs apply from the next login; without
ldap.tls.ca_certthe system trust store is used;ldap.hostmust be a
name matching the server certificate; theruamel.yamlrepair command
(the venv belongs to root); the "LDAP unreachable" troubleshooting;
manage.py unlock-ipandinstall.sh --confirm-anylisted. The service
unit's documentation link points to the repository.
Upgrade notes
- Existing directories need the new ACL rule by hand —
update.sh
never touches slapd. Followdocs/upgrade-1.25.md(also in the
WebGUI under Docs): back upcn=config, insert oneolcAccessrule,
check that an ordinary user no longer seesdescription. Until then
the TOTP secrets stay readable for directory users. Side effect: user
and service-account descriptions are no longer visible to ordinary
directory users either (SSSD does not use them).
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
- Directory users can no longer read the TOTP secrets. The LDAP
-
LDAP WebGUI v1.25.3
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 2m44sTests / pytest (Python 3.12) (push) Successful in 2m50sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 17sRelease / Publish release (push) Successful in 3sreleased this
2026-11-02 12:34:49 +01:00 | 16 commits to main since this releaseFixed
- An update can no longer leave a truncated
config.yaml. When a
release brought new configuration keys, the update emptied
config.yamlbefore writing the extended version, so a failure in that
moment cut off the secret key and the bind password. The new content is
now complete before the file is touched — the same guarantee the
Settings form got in 1.25.2. The update's snapshot already allowed a
rollback; now it is not needed for this case.
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
- An update can no longer leave a truncated
-
LDAP WebGUI v1.25.2
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 2m42sTests / pytest (Python 3.12) (push) Successful in 2m48sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 18sRelease / Publish release (push) Successful in 3sreleased this
2026-11-02 02:05:59 +01:00 | 17 commits to main since this releaseFixed
-
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 changedconfig.yamlon 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.timezonehad 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.
--allowto 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 -tundoes 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-sslit 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),/healthrules 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,locationor
serverblocks 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_DISABLEDto 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-webguiruns as the service user
(su ldapwebgui ldapwebguiin/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.shdoes not touch
/etc/logrotate.d/ldap-webgui— onlyinstall.shwrites it. On an
existing host, add thesuline by hand (as root):
sed -i '1a\ su ldapwebgui ldapwebgui' /etc/logrotate.d/ldap-webgui,
then check it withlogrotate -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 inapp.log
andsecurity.logmove 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
-
LDAP WebGUI v1.25.1
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 2m39sTests / pytest (Python 3.12) (push) Successful in 2m46sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 17sRelease / Publish release (push) Successful in 2sreleased this
2026-11-02 01:35:16 +01:00 | 18 commits to main since this releaseSecurity
- StartTLS checks the directory's certificate. With
tls.start_tls: trueon port 389 and notls.ca_cert, the connection was encrypted
but any certificate was accepted —tls.verifywas ignored, so an
attacker in the path could read the bind password and every login
password. It now verifies against the system trust store (or
ca_cert), as LDAPS always did. Check before updating: a directory
whose certificate the system does not trust now refuses the connection
— add its CA to/usr/local/share/ca-certificates/(then
update-ca-certificates) or settls.ca_cert. - Deleting a user removes their group memberships and sudo rules
first.memberUid,member/uniqueMemberandsudoUserentries
used to stay behind, so a new account created later under the same uid
inherited admin rights and sudo. If a reference cannot be removed the
account is not deleted and the page names the group or rule. - Group members are written as the directory spells the uid.
memberUidcompares case-sensitively, so addingJDoefor the account
jdoesilently granted nothing. - Your own account cannot be deleted under another spelling of your
uid. - The installer and the updater no longer follow a symlink at the
session store./var/lib/ldap-webguibelongs to the service user, so
code running as that user could replacesessionswith a link, and the
next install or update, running as root, set the link's target to 0700
(/etcor/usr, breaking the host). Both now refuse a symlink there
(the update fails at the state step and is rolled back) and create the
directory and set its mode as the service user. - One account, one 2FA lockout, whatever the spelling. The directory
matches user names case-insensitively, soAdminsigned in asadmin
— but the 2FA lockout and the guard against reusing a code were kept
per spelling. Every case variant got a fresh budget of 20 guesses
(defeating the permanent lock) and an observed code could be replayed
asADMIN. After the password check the login now uses the user name
as stored in the directory, for the session, the role check, the
lockouts and the log; the lockout stores ignore case, existing state
files included.manage.py unlock-totp,disable-2faand
set-passwordresolve the stored name too. - A successful login no longer wipes the failed attempts against other
accounts. The login limiter dropped an address's whole record on any
successful login, so someone with an account of their own could guess
another account's password without limit — four wrong guesses, one
correct login of their own, repeat. A success now takes back only the
failures counted for the account that signed in. - Changing your password signs out your other sessions. So do
disabling or replacing 2FA, an admin resetting your password (in the UI
or through a CSV import) and a reset withmanage.py: a
session opened with the old password ends on its next request (the
session that made the change stays signed in for the 2FA actions). The
change times are kept in/var/lib/ldap-webgui/credential_epochs.json. - The current-password check on change-password, 2FA disable and 2FA
replace is rate-limited. Someone holding a stolen session could try
passwords there as fast as the directory answered. Wrong passwords are
now counted per account with the login limit and lockout time; reaching
the limit signs the session out and is logged (REAUTH_LOCKOUT; an
attempt while locked isREAUTH_BLOCKED). State file:
/var/lib/ldap-webgui/reauth_lockouts.json. - Parallel requests no longer get extra guesses past a lockout. Both
the login limiter and the 2FA lockout checked and counted an attempt in
two steps, so requests already in flight were all evaluated when the
limit was reached. Checking and counting is now one locked step taken
before the password or code is verified. - A backup code works once, even when sent twice at the same time.
Two parallel verifications could both accept the same code, and a stale
write could bring back a code another request had just used. When the
directory refuses to mark the code used because it has already changed,
the attempt counts as a wrong code.
Upgrade notes
- StartTLS without
tls.ca_certnow verifies the certificate (see
Security) — a directory with an untrusted certificate stops working
until its CA is trusted. LDAPS and setups withca_certare unchanged. - Session store: if
/var/lib/ldap-webgui/sessionswas replaced by a
symlink on purpose, the update now stops and rolls back — set
LDAP_WEBGUI_SESSION_DIRinstead. - No
nginx/ldap-webgui.confchange.
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
- StartTLS checks the directory's certificate. With
-
LDAP WebGUI v1.25.0
StableSome checks failedTests / pytest (Python 3.11) (push) Failing after 2m48sTests / pytest (Python 3.12) (push) Failing after 2m49sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 18sRelease / Publish release (push) Successful in 3sreleased this
2026-11-02 00:00:03 +01:00 | 19 commits to main since this releaseAdded
- How long the certificates last. Settings → Certificates shows,
read-only and to both roles, the certificate nginx serves (HTTPS) and
the one the directory server presents to the WebGUI (LDAPS, or
StartTLS on 389) — subject, issuer, names, validity, SHA-256
fingerprint, whether it is self-signed — plus the configured
ldap.tls.ca_certwhen it is a single certificate. For the LDAP
certificate it also says whether it verifies against that CA file and
matchesldap.host. A certificate generated by the installer is marked
as such; equal fingerprints read one certificate for both. What is
measured is what the daemons serve, not the files on disk. - A banner from 30 days before a certificate expires — on every page,
for both roles, not dismissible: blue from 30 days, amber from 15, red
from 7 and once expired, naming the certificate and the date and
linking to the card. One banner at most (the worst certificate); a red
one sits above the access banner, the others below it. A certificate
that cannot be read is unknown on the card, with the reason, and never
a banner. - No page waits for a handshake: the results are cached in
/var/lib/ldap-webgui/cert-status.json(6 h, 30 min after a failure),
a stale cache is refreshed in the background after the page is shown
(3 s per handshake), and Check now on the card reads them at once.
Upgrade notes
- No
nginx/ldap-webgui.confchange.
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
- How long the certificates last. Settings → Certificates shows,