LoginSign Up
← Back to all sparks
G

GLAuth

INFRA · APIS
Velocity5.0

Lightweight LDAP authentication server for developers

glauth.github.io ↗

A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.

ldapopentelemetryauthenticationembedded-pluginsrisc-v
◆Current state
GLAuth's 2.5.0 in April was the substantial release: OpenTelemetry tracing wired through the handler and plugin packages plus otelsql, embedded plugins, RISC-V platform support, StartTLS and LDAPS brought to feature parity, and LDAP paging compatibility when proxying. The two releases since are corrective — rejecting disabled users on all backends during Bind, an arbitrary-password issue, and a release-time plugin compatibility check.
◆Where it's heading
The direction in 2.5.0 is toward being operable in production rather than merely functional: distributed tracing, a config watcher that notices files added to a directory, credentials no longer leaking at INFO log level, and a legacy behaviour mode so existing deployments can upgrade without changing semantics. The patches since suggest the authentication paths are getting scrutiny they had not previously had, with disabled-user handling inconsistent across backends until 2.5.1 fixed it.
◆Prediction
Expect the 2.5 line to keep taking small authentication-correctness fixes, with the embedded plugin mechanism and the release-time compatibility check pointing toward more attention on how third-party backends are built and shipped.

◆Recent moves

  1. 11d ago

    v2.5.2 checks plugin compatibility at release time

    A single change: plugin compatibility is verified when a release is cut. Process work, though it follows naturally from the embedded plugin mechanism 2.5.0 introduced.

    View source ↗
  2. 18d ago

    v2.5.1 rejects disabled users on every backend during Bind

    Disabled users could still bind on some backends; that is now consistent across all of them, alongside an arbitrary-password fix. Both are authentication-correctness bugs in the path that matters most for a directory server.

    View source ↗
  3. 3mo ago

    v2.5.0 wires OpenTelemetry tracing through GLAuth end to end

    ⚡ SPARK

    The release that changes what GLAuth is suitable for: OTLP tracing threaded through the handler and plugin packages and into SQL via otelsql, embedded plugins, StartTLS and LDAPS at feature parity, LDAP paging compatibility when proxying, and a legacy behaviour mode for existing deployments. Credentials also stop leaking at INFO log level.

    View source ↗