8 releases

0.1.7 Jun 9, 2021
0.1.6 Feb 23, 2021
0.1.3 Jan 6, 2021
0.1.2 Sep 7, 2020
0.1.0 May 25, 2020

#31 in Authentication

Download history 38/week @ 2021-02-24 28/week @ 2021-03-03 38/week @ 2021-03-10 48/week @ 2021-03-17 51/week @ 2021-03-24 48/week @ 2021-03-31 38/week @ 2021-04-07 138/week @ 2021-04-14 167/week @ 2021-04-21 70/week @ 2021-04-28 84/week @ 2021-05-05 87/week @ 2021-05-12 117/week @ 2021-05-19 83/week @ 2021-05-26 47/week @ 2021-06-02 67/week @ 2021-06-09

333 downloads per month

MPL-2.0 license

69KB
2K SLoC

Ldap3 Server (Protocol Bindings)

This is a work-in-progress of LDAP3 server and client capable protocol bindings.

This is not an LDAP3 server - it is the required parts to allow you to build one using a TCP server. You will and should develop your own server state machine, and should consider the many security risks of LDAP3 such as filter stack limits, request sizelimits, number of entries limited in results, binds and how you check access controls, and more.

Structure

This library contains all the needed protocol bindings, mapped to their BER structures in proto, as well as a set of simple wrappers of common operations required for a server, discarding many of the esoteric options that are generally not required.

Examples

There is an example hardcoded server using Actix in examples

ScoreCard

name from rfc implemented?
bind rfc4511 ✅ (only simple bind)
unbind rfc4511
search rfc4511
filter rfc4511 🔨 (excluding sub, ge, le, aprx, ext)
modify rfc4511
add rfc4511
delete rfc4511
modRDN rfc4511
compare rfc4511
abandon rfc4511
extended rfc4511 ✅ (may need changes)
whoami rfc4532
disconnection notice rfc4511

Things we probably won't add

StartTLS has a number of security issues compared to LDAPS, and should not be used, or developed as it is not only more complex, but also worse than LDAPS. Use LDAPS.

SASL is extremely complicated, and there are very few clients that require it over simple bind. It's not really worth the time to add it. If it is contributed, I will only accept SASL as an authentication mechanism - I won't accept the SASL transport encryption layer, as it's just too complicated. Again, use LDAPS.

Notes:

LDAP - the trashfire we have, not the trashfire we want.

Dependencies

~3MB
~51K SLoC