According to RFC 4511 section 5.1: The protocol elements of LDAP SHALL be encoded for exchange using the Basic Encoding Rules [BER] of [ASN.1] with the following restrictions [...] The library does not have much choice except accepting everything the server throws at it, therefore it makes sense using the more lax BER encoding to parse server responses. Using DER is still ok for the encoding part since DER is still a subset of BER, and anything accepting BER will accept DER too. |
||
|---|---|---|
| example | ||
| npm | ||
| src/Ldap | ||
| ssl | ||
| test | ||
| .gitignore | ||
| .travis.yml | ||
| .vim.custom | ||
| CHANGELOG.markdown | ||
| default.nix | ||
| Gemfile | ||
| Guardfile | ||
| ldap-client.cabal | ||
| LICENSE | ||
| package.nix | ||
| README.markdown | ||
| Setup.hs | ||
| shell.nix | ||
ldap-client
This library implements (the parts of) RFC 4511
Feature | RFC Section | Support
:--------------------------- |:---------------:|:-----------: Bind Operation | 4.2 | ✔ Unbind Operation | 4.3 | ✔ Unsolicited Notification | 4.4 | ✔ Notice of Disconnection | 4.4.1 | ✔ Search Operation | 4.5 | ✔* Modify Operation | 4.6 | ✔ Add Operation | 4.7 | ✔ Delete Operation | 4.8 | ✔ Modify DN Operation | 4.9 | ✔ Compare Operation | 4.10 | ✔ Abandon Operation | 4.11 | ✘ Extended Operation | 4.12 | ✔ IntermediateResponse Message | 4.13 | ✔ StartTLS Operation | 4.14 | ✔† LDAP over TLS | - | ✔
* The :dn thing is unsupported in Extensible matches
† Only serves as an example of Extended Operation. It's useless for all practical purposes as it does not actually enable TLS. In other words, use LDAP over TLS instead.