The Kentor AuthServices Owin middleware is designed to be used with an Owin authentication pipeline and is compatible with ASP.NET Identity. Kentor AuthServices provides external login in the same way as the built in Google, Facebook and Twitter providers.
To use the Kentor AuthServices middleware, it needs to be configured in
Startup.Auth.Cs.
app.UseKentorAuthServicesAuthentication(new KentorAuthServicesAuthenticationOptions());
The options class only contains the Owin-specific configuration (such as the name used to identify the login provider). The rest of the configuration is read from the web.config/app.config and configured in the same way as when using the http module or the MVC controller.
If you would like to provide the AuthServices-related configuration in code, specify false for
the loadConfiguration constructor parameter and then build the options based on your own
logic. For example:
var myAuthServicesOptions = new KentorAuthServicesAuthenticationOptions(false)
// more logic to set SPOptions, etc.
app.UseKentorAuthServicesAuthentication(myAuthServicesOptions);
You can see a full example of this in the SampleOwinApplication project included in the source code. See the Startup.Auth.cs file
An Owin-based application issues an AuthenticationResponseChallenge to ask the middleware to begin the authentication procedure. In that challenge, there is a properties dictionary. To use a specified idp, the entity id of the idp should be entered in that dictionary under the key "idp".
In a typical MVC application that requires some changes to the generated code
to enable passing a property to the AuthenticationProperties dictionary.
Another, more simple way to pass a value is to put it directly in the Owin environment dictionary under the key "KentorAuthServices.idp".
Here's an example of how to set the Owin environment value through ASP.NET MVC
var context = HttpContext.GetOwinContext();
context.Environment.Add("KentorAuthServices.idp", new EntityId(YOUR_IDP_ENTITY_ID));