-
LDAP WebGUI v1.31.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 27sTests / pytest (Python 3.11) (push) Successful in 19m11sTests / pytest (Python 3.13) (push) Successful in 20m20sTests / Publish release (push) Successful in 3sreleased this
2026-11-05 19:14:56 +01:00 | 8 commits to main since this releaseAdded
- Monitoring through Zabbix.
GET /healthwith
Authorization: Bearer <token>answers a read-only JSON status report
(schema 1): the live LDAP service bind, certificate expiry (HTTPS, LDAP
server, LDAP CA), update available, the last update run (web and
ldap-webgui-update), lockout counts, the daily config backup — each
cached part with its age. No addresses, paths or configuration values
but the LDAPhost:port: errors are fixed words (timeout,refused,
tls, …), the full text stays inapp.log. No session, no cookie; 200
whenever the report could be built, the state is in the body. Without the header
/healthanswers exactly as before. Only loopback, the admin hosts
and the monitoring hosts reach it — no nginx change. Guide:
docs/monitoring.md. - A Zabbix 7.0 template,
docs/zabbix/ldap_webgui_by_http.yaml
(also on the host under/opt/ldap-webgui/docs/zabbix/): one HTTP
agent request per minute, dependent items, certificate discovery, and
triggers for an LDAP bind failure, certificates at 30/15/7 days and
expired, an available update, a failing update check, a failed update
or rollback, permanent 2FA locks, login lockouts, a failed or stalled
config backup, a stalled status refresh and a report that stops
answering. TLS verification is on — the Zabbix server/proxy needs the
CA of the WebGUI's certificate. - Settings → Monitoring (below Access): generate or revoke the
token (full admins, password re-entry; the token is shown once, only
its SHA-256 is kept inconfig.yaml), the URL and header for Zabbix,
the number of monitoring hosts, the template download (both roles).
On the console:manage.py monitoring-token [--revoke]. Security log:
MONITORING_TOKEN_SET,MONITORING_TOKEN_REVOKED,
MONITORING_REAUTH_FAILED, andMONITORING_AUTH_FAILEDfor a refused
poll (throttled; a successful poll is never logged). ldap-webgui-status-refresh.timer, every 15 minutes as the service
user (manage.py refresh-status): refreshes the certificate data and
the update check, each only when its own interval has run out, so a
poll never waits for a handshake or the release source. Installed and
enabled byinstall.sh;update.shinstalls it and enables it only
where the timer is new on the host — a disabled timer stays disabled, a
masked one is left alone.
Changed
update.shrecords every real run — success, noop, failed,
rolled back, rollback failed; from the web UI or the console, not a dry
run or a preflight — in/var/lib/ldap-webgui-update/last-update.json.config-backup.shrecords each run in
/var/lib/ldap-webgui-backup/status.json(time, result, newest copy —
nothing of the config); the backup unit may write that directory./healthwithout a token unbinds its service connection after the
check.
Upgrade notes
- No vhost change. Updated from the web UI, with
ldap-webgui-update --from-release, or with theupdate.shof an
unpacked 1.31.0 archive, the refresh timer arrives installed and
enabled; nothing to do unless you want Zabbix to watch the host. - To use the report: put the Zabbix server — or its proxy — into the
monitoring hosts (Settings → Access whenldap-webgui-access.pathis
enabled, elseinstall.sh --allow-monitoring LIST, or the file
/etc/nginx/ldap-webgui-monitoring.confplus
nginx -t && systemctl reload nginx), generate a token under
Settings → Monitoring and import the template
(docs/monitoring.md). ldap-webgui-updatewithout--from-release(git mode, or
--archive) runs the clone'supdate.sh— still 1.30.0's, unless you
pulled the clone by hand — and that one carries out the whole update:
it knows neither the refresh timer nor the last-update record. Only
release mode switches to 1.31.0's ownupdate.shbefore changing
anything. After such an update re-apply 1.31.0 once with its own
update.sh—ldap-webgui-update --reinstall(git mode; the clone is
at 1.31.0 by then), or on a host without git access
bash <unpacked 1.31.0>/update.sh --archive <file> --reinstall: it
installs and enables the timer and writes the first record.
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
- Monitoring through Zabbix.