Skip to main content

OpenId Authentication with AspNet Identity Core

This is a very simple trick to make AspNet Identity work with OpenId Authentication. More of all both approach is completely separate to each other, there is no any connecting point.

I am using Microsoft.AspNetCore.Authentication.OpenIdConnect package to configure but it should work with any other.

Configuring under Startup.cs with IAppBuilder
 app.UseCookieAuthentication(new CookieAuthenticationOptions  
   AuthenticationScheme = CookieAuthenticationDefaults.AuthenticationScheme,  
   LoginPath = new PathString("/Account/Login"),  
   CookieName = "MyProjectName",  
   .UseOpenIdConnectAuthentication(new OpenIdConnectOptions  
     ClientId = "<AzureAdClientId>",  
     Authority = String.Format("{0}", "<AzureAdTenant>"),  
     ResponseType = OpenIdConnectResponseType.IdToken,  
     PostLogoutRedirectUri = "<my website url>",  
     AutomaticChallenge = false,  
     Events = new OpenIdConnectEvents  
       OnTicketReceived = OnTicketReceived,  
       //OnAuthenticationFailed = OnAuthenticationFailed,  
       //OnRemoteFailure = OnRemoteFailure  
     AuthenticationScheme = OpenIdConnectDefaults.AuthenticationScheme  

Over here there are two most important items to make compatible with AspNet Identity.
AutomaticChallenge = false, it would restrict from redirecting to OpenId Connect when a user comes to the site so that they would have the option to log in through OpenIdConnect or AspNet Identity.
OnTicketReceived = OnTicketReceived This is a delegate through which we can allow users coming from OpenIdConnect to register in our system through AspNet Identity. This is triggered once the user is authorized and successfully return to our website.

Implementation under AspNet Identity for  OnTicketReceived
The above delegate has a parameter to get System.Security.Claims.ClaimsPrincipal. So, a factory can be created to get data model for User.

To simplify we can create a function under UserManager to register user through Claims.

 public class MyProjectUserManager  
      : UserManager<User>  
      public async Task<IdentityResult> CreateAsync(ClaimsPrincipal claimsPrincipal)  
           if (principal == null || !principal.Claims.Any())  
                throw new ArgumentException(nameof(principal));  
           // TODO: Compose user based on need.  
           var user = new User  
                UserName = principal.FindFirst(c => c.Type == ClaimTypes.Name)?.Value,  
                Email = principal.FindFirst(c => c.Type == ClaimTypes.Email)?.Value,  
           return await CreateAsync(user);  

That is all we need. Now the implementation of OnTicketReceived is simple.

 private async Task OnTicketReceived(TicketReceivedContext ticketReceivedContext)  
   // TODO: Need to be registered in service collection and set ServiceProvider is 
   //       property to get services. Which can done through services.BuildServiceProvider()
   var userManager = ServiceProvider.GetService<MyProjectUserManager>();  
   await userManager.CreateAsync(ticketReceivedContext.Principal);  


Popular posts from this blog

Architecture solution composting Repository Pattern, Unit Of Work, Dependency Injection, Factory Pattern and others

Project architecture is like garden, we plant the things in certain order and eventually they grow in similar manner. If things are planted well then they will all look(work) great and easier to manage. If they grow as cumbersome it would difficult to maintain and with time more problems would be happening in maintenance.

There is no any fixed or known approach to decide project architecture and specially with Agile Methodology. In Agile Methodology, we cannot predict how our end products will look like similarly we cannot say a certain architecture will fit well for entire development lifespan for project. So, the best thing is to modify the architecture as per our application growth. I understand that it sounds good but will be far more problematic with actual development. If it is left as it is then more problems will arise with time. Just think about moving plant vs a full grown tree.

Coming to technical side, In this article, I will be explaining about the various techniques tha…

LDAP with ASP.Net Identity Core in MVC with project.json

Lightweight Directory Access Protocol (LDAP), the name itself explain it. An application protocol used over an IP network to access the distributed directory information service.

The first and foremost thing is to add references for consuming LDAP. This has to be done by adding reference from Global Assembly Cache (GAC) into project.json

"frameworks": { "net461": { "frameworkAssemblies": { "System.DirectoryServices": "", "System.DirectoryServices.AccountManagement": "" } } },
These System.DirectoryServices and System.DirectoryServices.AccountManagement references are used to consume LDAP functionality.

It is always better to have an abstraction for irrelevant items in consuming part. For an example, the application does not need to know about PrincipalContext or any other dependent items from those two references to make it extensible. So, we can begin with some bas…

Configuring Ninject, Asp.Net Identity UserManager, DataProtectorTokenProvider with Owin

It can be bit tricky to configure both Ninject and Asp.Net Identity UserManager if some value is expected from DI to configure UserManager. We will look into configuring both and also use OwinContext to get UserManager.

As usual, all configuration need to be done on Startup.cs. It is just a convention but can be used with different name, the important thing is to decorate class with following attribute to make it Owin start-up:

[assembly: OwinStartup(typeof(MyProject.Web.Startup))]
Ninject configuration

Configuring Ninject kernel through method which would be used to register under Owin.

public IKernel CreateKernel() { var kernel = new StandardKernel(); try { //kernel.Bind<IHttpModule>().To<HttpApplicationInitializationHttpModule>(); // TODO: Put any other injection which are required. return kernel; } catch { kernel.Dispose(); throw; }…