← Back to all sparks
G

GLAuth

INFRA · APIS
Velocity0.0

Lightweight LDAP authentication server for developers

GLAuth's September releases are security dependency updates and build fixes.

ldapauthenticationsecuritymaintenanceopentelemetry
◆Current state
GLAuth's 2.5.0 in April was the substantial release, adding OpenTelemetry tracing, embedded plugins and RISC-V builds. Since then releases have been corrective: disabled users rejected on all backends in 2.5.1, a release-time plugin check in 2.5.2, a port-handling fix in 2.5.3, and 2.5.4 on September 13 updating all dependencies to safe versions.
◆Where it's heading
GLAuth is in maintenance after 2.5.0, with occasional security and build releases. No new features have shipped since April.
◆Prediction
Expect occasional 2.5.x security updates; the entries give no sign of the next feature release.

◆Recent moves

  1. 1mo ago

    GLAuth 2.5.4 updates all dependencies for security

    A security release that updates all dependencies to safe versions. It is the latest step in GLAuth's maintenance phase since 2.5.0.

    View source ↗
  2. 1mo ago

    GLAuth 2.5.3 restores arbitrary port in tests

    Build and test fixes that restore arbitrary port support and trim repetition. No user-facing change beyond that.

    View source ↗
  3. 3mo 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 ↗
  4. 3mo 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 ↗
  5. 6mo 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 ↗