GLAuth
GLAuth-v2.5.2 open-sourceThe section your link pointed to isn't on GLAuth's page any more, so we've brought you to the top.
GLAuth is a secure, easy-to-use LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. authentication server with configurable backends for centralizing account management across infrastructure.
Summary
GLAuth is an open-source LDAP authentication server, released under the MIT license, that runs as a single portable executable rather than a full directory service deployment. You configure it with a file and start it directly on the OS of your choice, storing user data in flat files, S3, a SQL database, or by proxying to an existing LDAP server, and it supports two-factor authentication and TLS. It's aimed at developers and system administrators who need to centralize account, SSH key, and password management across Linux and OSX machines without standing up Active DirectoryActive DirectoryMicrosoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. or OpenLDAPOpenLDAPAn open-source implementation of the Lightweight Directory Access Protocol, maintained by the OpenLDAP Project, used to store and query structured identity data like users and groups over a network., and its README describes it as a lightweight alternative to both, usable either as a gateway in front of legacy systems or standalone. The project dates to 2014, has drawn 50 contributors, and remains active with 17 releases in the tracked window and its most recent one 27 days ago.
GLAuth is a secure, easy-to-use LDAP authentication server with configurable backends for centralizing account management across infrastructure.
How GLAuth helps
How do I let every Linux and OSX machine on my network check the same set of accounts and SSH keys without standing up Active Directory or OpenLDAP?
it runs as one portable executable reading a config file, so any host pointed at it over LDAP resolves against a single user list instead of a locally-replicated one
Can I add security to a legacy application without rewriting how it authenticates?
it sits in front of the existing system as a gateway and injects Two-Factor or TLS on top of the traffic it already speaks, so the application keeps using plain LDAP calls
Where should the actual user records live?
the config points at flat files, S3, a SQL database, or an existing LDAP server, and GLAuth answers LDAP queries from whichever one it's pointed at
Can I chain more than one backend to build up the features I need?
multiple backends can be linked together so features like Two-Factor are injected as the request passes through, rather than requiring one backend to do everything
How do I confirm the server is actually answering authentication requests before I put it in front of real systems?
standard LDAP tooling can bind and search against its listen address, so a query returning the expected entries confirms it's serving correctly before anything depends on it
What happens to my SSH key and password management as I add more cloud servers?
since accounts, keys, and passwords are centralized in the one directory it serves, adding a server means pointing it at the same GLAuth instance rather than maintaining separate local account lists
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for GLAuth, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail GLAuth puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
13 entries
No entries match these filters.
- July 20261
- April 20261
- April 20251
- February 20241
- September 20231
- July 20231
- November 20221
- February 20221
- November 20211
- August 20211
- February 20201
- December 20181
- July 20181
Project health
Issue, contributor and maintainer activity in glauth/glauth, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 5 +2 vs prior 12 months
- Maintainers 1 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 3.6 days first maintainer reply 3.6 days
- Open backlog 78 of 220 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 78
- Contributors / month 2
- Commits / month 10
- Stars 2,851
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.