GLAuth is a lightweight, easy-to-use LDAP server designed to centrally manage authentication and account data for development, home use, or CI environments.
A lightweight LDAP server for development, home use, or CI
GLAuth is primarily used to centralize user account management, SSH keys, and passwords across various infrastructure components such as Linux servers, OSX machines, and support applications like Jenkins or Apache. It is ideal for developers, system administrators, and homelab enthusiasts who need a lightweight alternative to full LDAP solutions like OpenLDAP or Active Directory, especially in non-production or small-scale environments.
For production use, it is critical to configure SSL/TLS to secure LDAP traffic. GLAuth supports multiple backends and chaining, allowing flexible deployment architectures. Users should base pull requests on the 'dev' branch and format code using 'gofmt'. While suitable for lightweight and development environments, it may not replace full-featured enterprise LDAP solutions in large-scale deployments.
Download a precompiled binary from the releases page
Download the example configuration file from the repository
Start the GLAuth server with the config file using `./glauth64 -c sample-simple.cfg`
For production, configure SSL/TLS certificates for secure LDAPS
Optionally, use configuration management tools like Puppet, Chef, or Ansible for deployment./glauth64 -c sample-simple.cfg
Starts the GLAuth server using the specified configuration file
ldapsearch -LLL -H ldap://localhost:3893 -D cn=serviceuser,ou=svcaccts,dc=glauth,dc=com -w mysecret -x -bdc=glauth,dc=com cn=hackers
Tests the LDAP server with a search query for a user entry
glauth -c <file|s3url>
Run GLAuth with a local config file or S3 URL configuration
--ldap <address>
Specify the listen address for the LDAP server
--ldaps <address>
Specify the listen address for the LDAPS (secure LDAP) server
--ldaps-cert <cert-file>
Path to the TLS certificate file for LDAPS
--ldaps-key <key-file>
Path to the TLS key file for LDAPS
-K <aws_key_id> -S <aws_secret_key> -r <aws_region>
Provide AWS credentials and region for S3 backend configuration