Sample project showing how to do headless Kerberos authentication with Auth0 (for Console Applications, Windows Services, ...)
MIT License
Sample project showing how to do headless Kerberos authentication with Auth0 (for Console Applications, Windows Services, ...)
Use "Integrated Windows Authentication" (Kerberos) from your Console applications, Windows Services, ... with Auth0. This allows you to have Kerberos support for headless application that run in the context of a Windows User (on a Domain Joined machine).
First you'll need to configure your application in Auth0. Add the following URL as a Callback URL in Auth0:
http://headless.local
Then add the required settings in the App.config/Web.config:
<add key="auth0:Domain" value="fabrikam.auth0.com" />
<add key="auth0:ClientID" value="yNqQMENaYIONxAaQmrct341tZ9joEjTi" />
<add key="auth0:ConnectionName" value="FabrikamAD" />
And now you can use the AdConnectorClient
for headless Kerberos authentication and to get a token for the current user:
var client = new AdConnectorClient(
ConfigurationManager.AppSettings["auth0:Domain"],
ConfigurationManager.AppSettings["auth0:ClientID"],
ConfigurationManager.AppSettings["auth0:ConnectionName"],
"openid email nickname");
var result = client.Authenticate();
foreach (var item in result)
{
Console.WriteLine(" > {0}: {1}", item.Key, String.Join(", ", item.Value));
}
Note: Since you can specify the scope used for authentication, you can ask for additional information or even request a refresh token.
Example:
Auth0 helps you to:
If you have found a bug or if you have a feature request, please report them at this repository issues section. Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
This project is licensed under the MIT license. See the LICENSE file for more info.