How to get current user in asp net core

Question

I want to get a current user for getting information of a user such as an email  But I can t do that in asp net core  I m so confused This is my code    HttpContext almost is null in constructor of controller  It s not good to get a user in each action  I Wanna get information of user once and set them into ViewData   public DashboardController         var user   HttpContext User GetUserId

User · Answer

If you are using the scafolded Identity and using Asp net Core 2 2  you can access the current user from a view like this    using Microsoft AspNetCore Identity  inject SignInManager lt IdentityUser gt  SignInManager  inject UserManager lt IdentityUser gt  UserManager    if  SignInManager IsSignedIn User                  lt p gt Hello  User Identity Name  lt  p gt            else                lt p gt You re not signed in  lt  p gt          https   docs microsoft com en-us aspnet core security authentication identity view aspnetcore-2 2 amp tabs visual-studio

User · Answer

It would appear that as of now  April of 2017  that the following works   public string LoggedInUser   gt  User Identity Name    At least while within a Controller

User · Answer

Simple way that works and I checked   private readonly UserManager lt IdentityUser gt   userManager  public CompetitionsController UserManager lt IdentityUser gt  userManager         userManager   userManager     var user   await  userManager GetUserAsync HttpContext User     then you can all the properties of this variables like user Email  I hope this would help someone   Edit   It s an apparently simple thing but bit complicated cause of different types of authentication systems in ASP NET Core  I update cause some people are getting null   For JWT Authentication  Tested on ASP NET Core v3 0 0-preview7    var email   HttpContext User Claims FirstOrDefault c   gt  c Type     sub    Value   var user   await  userManager FindByEmailAsync email

User · Answer

Taking IdentityUser would also work  This is a current user object and all values of user can be retrieved   private readonly UserManager lt IdentityUser gt   userManager  public yourController UserManager lt IdentityUser gt  userManager         userManager   userManager     var user   await  userManager GetUserAsync HttpContext User

User · Answer

I have to say I was quite surprised that HttpContext is null inside the constructor  I m sure it s for performance reasons  Have confirmed that using IPrincipal as described below does get it injected into the constructor  Its essentially doing the same as the accepted answer  but in a more interfacey-way   For anyone finding this question looking for an answer to the generic  quot How to get current user  quot  you can just access User directly from Controller User  But you can only do this inside action methods  I assume because controllers don t only run with HttpContexts and for performance reasons   However - if you need it in the constructor  as OP did  or need to create other  injectable objects that need the current user then the below is a better approach  Inject IPrincipal to get user First meet IPrincipal and IIdentity public interface IPrincipal       IIdentity Identity   get        bool IsInRole string role      public interface IIdentity       string AuthenticationType   get        bool IsAuthenticated   get        string Name   get       IPrincipal and IIdentity represents the user and username  Wikipedia will comfort you if  Principal  sounds odd  Important to realize that whether you get it from IHttpContextAccessor HttpContext User  ControllerBase User or ControllerBase HttpContext User you re getting an object that is guaranteed to be a ClaimsPrincipal object which implements IPrincipal  There s no other type of User that ASP NET uses for User right now   but that s not to say other something else couldn t implement IPrincipal   So if you have something which has a dependency of  the current user name  that you want injected you should be injecting IPrincipal and definitely not IHttpContextAccessor  Important  Don t waste time injecting IPrincipal directly to your controller  or action method - it s pointless since User is available to you there already  In startup cs        Inject IPrincipal    services AddTransient lt IPrincipal gt  provider   gt  provider GetService lt IHttpContextAccessor gt    HttpContext User    Then in your DI object that needs the user you just inject IPrincipal to get the current user  The most important thing here is if you re doing unit tests you don t need to send in an HttpContext  but only need to mock something that represents IPrincipal which can just be ClaimsPrincipal  One extra important thing that I m not 100  sure about  If you need to access the actual claims from ClaimsPrincipal you need to cast IPrincipal to ClaimsPrincipal  This is fine since we know 100  that at runtime it s of that type  since that s what HttpContext User is   I actually like to just do this in the constructor since I already know for sure any IPrincipal  will be a ClaimsPrincipal  If you re doing mocking  just create a ClaimsPrincipal directly and pass it to whatever takes IPrincipal  Exactly why there is no interface for IClaimsPrincipal I m not sure  I assume MS decided that ClaimsPrincipal was just a specialized  collection  that didn t warrant an interface

User · Answer

In addition to existing answers I d like to add that you can also have a class instance available app-wide which holds user-related data like UserID etc    It may be useful for refactoring e g  you don t want to fetch UserID in every controller action and declare an extra UserID parameter in every method related to Service Layer   I ve done a research and here s my post   You just extend your class which you derive from DbContext by adding UserId property  or implement a custom Session class which has this property    At filter level you can fetch your class instance and set UserId value   After that wherever you inject your instance - it will have the necessary data  lifetime must be per request  so you register it using AddScoped method    Working example   public class AppInitializationFilter   IAsyncActionFilter       private DBContextWithUserAuditing  dbContext       public AppInitializationFilter          DBContextWithUserAuditing dbContext                          dbContext   dbContext             public async Task OnActionExecutionAsync          ActionExecutingContext context          ActionExecutionDelegate next                         string userId   null          int  tenantId   null           var claimsIdentity    ClaimsIdentity context HttpContext User Identity           var userIdClaim   claimsIdentity Claims SingleOrDefault c   gt  c Type    ClaimTypes NameIdentifier           if  userIdClaim    null                        userId   userIdClaim Value                     var tenantIdClaim   claimsIdentity Claims SingleOrDefault c   gt  c Type    CustomClaims TenantId           if  tenantIdClaim    null                        tenantId    string IsNullOrEmpty tenantIdClaim Value    int Parse tenantIdClaim Value     int  null                      dbContext UserId   userId           dbContext TenantId   tenantId           var resultContext   await next              For more information see my answer

User · Answer

Have another way of getting current user in Asp NET Core - and I think I saw it somewhere here  on SO          Stores UserManager private readonly UserManager lt ApplicationUser gt   manager       Inject UserManager using dependency injection     Works only if you choose  Individual user accounts  during project creation  public DemoController UserManager lt ApplicationUser gt  manager             manager   manager          You can also just take part after return and use it in async methods  private async Task lt ApplicationUser gt  GetCurrentUser             return await  manager GetUserAsync HttpContext User             Generic demo method  public async Task DemoMethod             var user   await GetCurrentUser         string userEmail   user Email     Here you gets user email      string userId   user Id        That code goes to controller named DemoController  Won t work without both await  won t compile

User · Answer

I got my solution   var claim   HttpContext User CurrentUserID     public static class XYZ       public static int CurrentUserID this ClaimsPrincipal claim                var userID   claimsPrincipal Claims ToList   Find r   gt  r Type               UserID   Value          return Convert ToInt32 userID             public static string CurrentUserRole this ClaimsPrincipal claim                var role   claimsPrincipal Claims ToList   Find r   gt  r Type              Role   Value          return role

User · Answer

My problem was to access the logged in User as an object in the cshtml file  Considering you wanted the user in ViewData  this approach might be helpful   In the cshtml file   using Microsoft AspNetCore Identity  inject UserManager lt ApplicationUser gt  UserManager   lt  DOCTYPE html gt   lt html gt     lt head gt       lt meta charset  utf-8  gt       lt title gt       UserManager FindByNameAsync UserManager GetUserName User   Result Email      lt  title gt     lt  head gt     lt body gt      lt  body gt   lt  html gt

User · Answer

Most of the answers show how to best handle HttpContext from the documentation  which is also what I went with    I did want to mention that you ll want to check you project settings when debugging  the default is Enable Anonymous Authentication   true

User · Answer

User FindFirst ClaimTypes NameIdentifier  Value   EDIT for constructor  Below code works   public Controller IHttpContextAccessor httpContextAccessor        var userId   httpContextAccessor HttpContext User FindFirst ClaimTypes NameIdentifier  Value      Edit for RTM  You should register IHttpContextAccessor       public void ConfigureServices IServiceCollection services                services AddHttpContextAccessor

User · Answer

Perhaps I didn t see the answer  but this is how I do it     Net Core --  Properties --  launchSettings json   You need to have change these values   windowsAuthentication   true     needs to be true  anonymousAuthentication   false      needs to be false    Startup cs --  ConfigureServices       services AddSingleton lt IHttpContextAccessor  HttpContextAccessor gt       MVC or Web Api Controller  private readonly IHttpContextAccessor  httpContextAccessor    constructor then  httpContextAccessor   httpContextAccessor    Controller method   string userName    httpContextAccessor HttpContext User Identity Name    Result is userName e g     Domain username

User · Answer

This is old question but my case shows that my case wasn t discussed here   I like the most the answer of Simon Weaver  https   stackoverflow com a 54411397 2903893   He explains in details how to get user name using IPrincipal and IIdentity  This answer is absolutely correct and I recommend to use this approach  However  during debugging I encountered with the problem when ASP NET can NOT populate service principle properly   or in other words  IPrincipal Identity Name is null   It s obvious that to get user name MVC framework should take it from somewhere  In the  NET world  ASP NET or ASP NET Core is using Open ID Connect middleware  In the simple scenario web apps authenticate a user in a web browser  In this scenario  the web application directs the user   s browser to sign them in to Azure AD  Azure AD returns a sign-in response through the user   s browser  which contains claims about the user in a security token   To make it work in the code for your application  you ll need to provide the authority to which you web app delegates sign-in   When you deploy your web app to Azure Service the common scenario to meet this requirements is to configure web app   App Services  -  YourApp -   Authentication   Authorization  blade -   App Service Authenticatio     On  and so on  https   github com Huachao azure-content blob master articles app-service-api app-service-api-authentication md   I beliebe  this is my educated guess  that under the hood of this process the wizard adjusts  parent  web config of this web app by adding the same settings that I show in following paragraphs  Basically  the issue why this approach does NOT work in ASP NET Core is because  parent  machine config is ignored by webconfig   this is not 100  sure  I just give the best explanation that I have   So  to meke it work you need to setup this manually in your app    Here is an article that explains how to manyally setup your app to use Azure AD  https   github com Azure-Samples active-directory-aspnetcore-webapp-openidconnect-v2 tree aspnetcore2-2  Step 1  Register the sample with your Azure AD tenant   it s obvious  don t want to spend my time of explanations    Step 2  In the appsettings json file  replace the ClientID value with the Application ID from the application you registered in Application Registration portal on Step 1  replace the TenantId value with common  Step 3  Open the Startup cs file and in the ConfigureServices method  after the line containing  AddAzureAD insert the following code  which enables your application to sign in users with the Azure AD v2 0 endpoint  that is both Work and School and Microsoft Personal accounts   services Configure lt OpenIdConnectOptions gt  AzureADDefaults OpenIdScheme  options   gt        options Authority   options Authority     v2 0        options TokenValidationParameters ValidateIssuer   false        Summary  I ve showed one more possible issue that could leed to an error that topic starter is explained  The reason of this issue is missing configurations for Azure AD  Open ID middleware   In order to solve this issue I propose manually setup  Authentication   Authorization   The short overview of how to setup this is added

User · Answer

I know there area lot of correct answers here  with respect to all of them I introduce this hack   In StartUp cs services AddSingleton lt IHttpContextAccessor  HttpContextAccessor gt      and then everywhere you need HttpContext you can use   httpContext   new HttpContextAccessor   HttpContext   Hope it helps

[c#] How to get current user in asp.net core

Examples related to c#

Examples related to asp.net-core

Examples related to asp.net-identity