LDAP client library - .NET Standard 2.0/2.1 - compatible .NET platforms: .NET >= NET5, .NET Core >= 2.0, .NET Framework >= 4.6.1, Universal Windows Platform, Xamarin (see here for a more detailed description of supported platforms https://docs.microsoft.com/en-us/dotnet/articles/standard/library ).
It works with any LDAP protocol compatible directory server (including Microsoft Active Directory).
The library is originally coming from Novell (https://www.novell.com/developer/ndk/ldap_libraries_for_c_sharp.html) - really old code base - looks like a tool-based conversion from Java - this is the original java code repo http://www.openldap.org/devel/gitweb.cgi?p=openldap-jldap.git;a=summary (first commit in that repo is from 2000 :)) - which explains some of the weirdness of the code base.
The Novell documentation for the original library:
- html: https://www.novell.com/documentation/developer/ldapcsharp/?page=/documentation/developer/ldapcsharp/cnet/data/front.html
- pdf: https://www.novell.com/documentation/developer/ldapcsharp/pdfdoc/cnet/cnet.pdf
First commit in this repo is the original C# source code from Novell. Next around 20 commits are my changes in order to port the code base to run on .NET Standard.
See ChangeLog for summary of changes.
There are a number of functional tests - running against OpenDJ on ubuntu during CI - which are also run as stress tests (e.g. the functional tests running on multiple threads) running against OpenLDAP on Ubuntu.
Sample usage
await using (var cn = new LdapConnection())
{
// connect
await cn.ConnectAsync("<<hostname>>", 389);
// bind with an username and password
// this how you can verify the password of an user
await cn.BindAsync("<<userdn>>", "<<userpassword>>");
// call ldap op
// await cn.DeleteAsync("<<userdn>>")
// await cn.AddAsync(<<ldapEntryInstance>>)
}Contributions and bugs reports are welcome.
The library has some samples which are not included in the solution and are in the original state (see original_samples folder) - they may or may not compile on .NET Standard - but they should be compilable on .NET Standard with minimal work.
