ldap4net | OpenLdap port for DotNet Core | Identity Management library

by flamencist C# Version: v2.7.14 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | ldap4net Summary

ldap4net is a C# library typically used in Security, Identity Management, Chef applications. ldap4net has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

OpenLdap port for DotNet Core (Linux\OSX\Windows)

Support

Quality

Security

License

Reuse

Support

ldap4net has a low active ecosystem.

It has 178 star(s) with 31 fork(s). There are 10 watchers for this library.

It had no major release in the last 12 months.

There are 34 open issues and 66 have been closed. On average issues are closed in 142 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of ldap4net is v2.7.14

Quality

ldap4net has 0 bugs and 0 code smells.

Security

ldap4net has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ldap4net code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

ldap4net is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

ldap4net releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ldap4net

Get all kandi verified functions for this library.

ldap4net Key Features

No Key Features are available at this moment for ldap4net.

ldap4net Examples and Code Snippets

No Code Snippets are available at this moment for ldap4net.

Community Discussions

Trending Discussions on ldap4net

.NET Core 2.1 Linux Keycloak integration\authentication (OpenID Connect + SSSD)

QUESTION

.NET Core 2.1 Linux Keycloak integration\authentication (OpenID Connect + SSSD)

Asked 2019-Feb-23 at 20:36

I am kinda lost now, I want to implement centralised user management here, and we have .NET Core 2.1 Web MVC app hosted on Linux, which uses Identity.EntityFrameworkCore to store users' information. Also we have FreeIPA for user management which is basically Kerberos authentication on LDAP directory.

As it's deployed on Linux I can't use WindowsAuthentication to use Kerberos, and also there is no standard way to use LDAP without Windows Compatibility Pack. The only way that is left is to use third-party library, but unfortunately I'm really new to .NET Core and C#, so here's what I'm trying to do:

Store user information (roles\claims\credentials) inside LDAP to implement centralised user management (now using database tables)
I want to implement SSO, this is possible via Kerberos Negotiate authentication, but now I can't find a way to use this on Linux. Also it's possible with app-> redirect to Keycloak -> Kerberos->OpenID Connect -> app, but I'd be glad to find solution with Kerberos

Well, I found bunch of third-party libraries like this, this and the whole bunch of THIS, and they all look promising, but I didn't found any with enough documentation or examples to use with .NET Core Identity.

As I said, I'm complete newbie in C# and .NET overall, and I'm unfortunately don't have an idea about either which of this library is better or is there any for straightforward way to use them to store and authenticate users.

P.S I know this question is dumb, but for learning purposes I had to make one. Any help with this would be appreciated!

...

ANSWER

Answered 2019-Feb-23 at 20:36

Well, looks like I mostly found the answer, but it has some caveats anyway. I used the Keycloak OpenID Connect setup with SSSD federation, because LDAP is the wrong approach for my goals anyway. More about that setup you can read here, I faced some stupid moments over there, most of them are predicted and bypassed in this guide, but that's more a FreeIPA + Keycloak thread. Last Keycloak thing that should be noted: I had to add and allow HBAC "keycloak" service to make it work, because otherwise my SSSD authentication was denied. Going forward to the .NET Core part: my app is 2.1, and my setup looks like that:

I added the following into Startup.cs dependencies:

Source https://stackoverflow.com/questions/54281210

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ldap4net

You can download it from GitHub.

Support

Most of popular Linux distributivesFreeBSDOSXWindowsSupported on the .NET Standard - minimum required is 2.0 - compatible .NET runtimes: .NET Core, Mono, .NET Framework.

Find more information at: