|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
333 downloads per month
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.
This library contains all the needed protocol bindings, mapped to their BER structures
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.
There is an example hardcoded server using Actix in
|bind||rfc4511||✅ (only simple bind)|
|filter||rfc4511||🔨 (excluding sub, ge, le, aprx, ext)|
|extended||rfc4511||✅ (may need changes)|
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.
LDAP - the trashfire we have, not the trashfire we want.