No description
- Rust 95.5%
- HTML 3.2%
- CSS 1.3%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| src | ||
| vendor/dn_escape | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
llldap
[!IMPORTANT ] You may be looking for lldap instead, a more mature solution with a different feature set.
Is your Lightweight Directory Access Protocol server too heavy and too cumbersome? If your lldap not light enough or are you looking for a solution which supports virtualhosts and multiple-value attributes such as mail aliases? llldap might be just for you!*
Comparison to lldap
Compared to lldap, llldap:
- does not use an SQLite database, but simple text files
- does not use GraphQL to build an API, and therefore does not require custom logic in the client (JS/WASM)
- supports virtualhosts out-of-the-box
- supports mailalias with multiple values in search queries
Potential future features
We may explore in the future:
- hierarchical groups
- fine-grained permissions (RBAC)
- running with different async runtimes
- implying base DN from HTTP HOST header (to have
auth.a.localhostandauth.b.localhostwhere users can login without adding the domain part) - making the core logic reusable as a library for custom LDAP behavior
- per-user/domain data retention policies to keep logs of login attempts
- per-domain admins