-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GSSAPI/Windows SASL authentication #28
Comments
To my understanding this could be done via kerberos tickets, and a bind via GSSAPI. For later see issue #7. |
@gfoidl is correct - this is how is supposed to work, but is not implemented. |
Is this implemented in the latest code? |
the GSSAPI data can be produced on Windows with InitializeSecurityContext The data provided by GSSAPI "just" need to be embedded into LDAP. I can help: I can write a prototype to produce the GSSAPI data if someone is doing the LDAP part to embed it. For linux, after some research, it seems that the API to use is gss_init_sec_context. |
Have you looked at what's been done here? maybe something over there will help. That project's kerberos authentication does appear to work, at least in my simple tests. |
Actually this library IS extensible enough to be able to implement your own SASL provider. I actually managed to implement auth into Ldap using Kerberos tickets via SPNEGO. Implementing InitializeSecurityContext may be actually even easier. Just look at RegisterSaslClientFactory and the whole ISaslClientFactory/ISaslClient interfaces and their realization. |
Has there been any movement on this? Would love to know if anyone has a good pattern setup that actually implements this properly. |
Hey guys, take a look at ldap4net:
|
Honestly, I like this library more, it is more easily extensible, doesn't have a dependency on a non-C# library and allows mixing with Kerberos.NET - and as a result authenticating with an already existing Kerberos TGT. |
@Evengard: Even then, seems to be based on the same base library as Novell. |
I was looking through the source code for LdapBindRequest and RfcBindRequest, and it doesn't appear to be any way to use the currently logged in Windows User for authentication in the case of connecting to an Active Directory server.
Is there any possibility of support this scenario? Ideally, I would like to run my .NET Core service as a specific user and let the that user's identity be used for the Ldap "bind" rather than storing username and password in my application's configuration.
The text was updated successfully, but these errors were encountered: