ASP NET MVC 5 - Identity How to get current ApplicationUser

Question

I have an Article entity in my project which has the ApplicationUser property named Author  How can I get the full object of currently logged ApplicationUser  While creating a new article  I have to set the Author property in Article to the current ApplicationUser   In the old Membership mechanism it was simple  but in the new Identity approach I don t know how to do this   I tried to do it this way    Add using statement for Identity extensions  using Microsoft AspNet Identity  Then I try to get the current user  ApplicationUser currentUser   db Users FirstOrDefault x   gt  x Id    User Identity GetUserId       But I get the following exception      LINQ to Entities does not recognize the method  System String GetUserId System Security Principal IIdentity   method  and this method cannot be translated into a store expression      Source EntityFramework

User · Answer

The code of Ellbar works  You need only add using   1 - using Microsoft AspNet Identity   And    the code of Ellbar   2 - string currentUserId   User Identity GetUserId    ApplicationUser currentUser   db Users FirstOrDefault x   gt  x Id    currentUserId    With this code  in currentUser   you work the general data of the connected user  if you want extra data    see this link

User · Answer

Its in the comments of the answers but nobody has posted this as the actual solution   You just need to add a using statement at the top   using Microsoft AspNet Identity

User · Answer

For MVC 5 just look inside the EnableTwoFactorAuthentication method of ManageController in WebApplication template scaffold  its being done there            HttpPost           ValidateAntiForgeryToken          public async Task lt ActionResult gt  EnableTwoFactorAuthentication                         await UserManager SetTwoFactorEnabledAsync User Identity GetUserId    true               var user   await UserManager FindByIdAsync User Identity GetUserId                 if  user    null                                await SignInManager SignInAsync user  isPersistent  false  rememberBrowser  false                             return RedirectToAction  Index    Manage                The answer is right there as suggested by Microsoft itself   var user   await UserManager FindByIdAsync User Identity GetUserId       It will have all the additional properties you defined in ApplicationUser class

User · Answer

Right now the asp mvc project template creates an account controller that gets the usermanager this way   HttpContext GetOwinContext   GetUserManager lt ApplicationUserManager gt      The following works for me   ApplicationUser user   HttpContext GetOwinContext   GetUserManager lt ApplicationUserManager gt    FindById User Identity GetUserId

User · Answer

My mistake  I shouldn t have used a method inside a LINQ query   Correct code   using Microsoft AspNet Identity    string currentUserId   User Identity GetUserId    ApplicationUser currentUser   db Users FirstOrDefault x   gt  x Id    currentUserId

User · Answer

ApplicationDbContext context   new ApplicationDbContext    var UserManager   new UserManager lt ApplicationUser gt  new UserStore lt ApplicationUser gt  context    ApplicationUser currentUser   UserManager FindById User Identity GetUserId      string ID   currentUser Id  string Email   currentUser Email  string Username   currentUser UserName

User · Answer

You should not need to query the database directly for the current ApplicationUser   That introduces a new dependency of having an extra context for starters  but going forward the user database tables change  3 times in the past 2 years  but the API is consistent  For example the users table is now called AspNetUsers in Identity Framework  and the names of several primary key fields kept changing  so the code in several answers will no longer work as-is   Another problem is that the underlying OWIN access to the database will use a separate context  so changes from separate SQL access can produce invalid results  e g  not seeing changes made to the database   Again the solution is to work with the supplied API and not try to work-around it   The correct way to access the current user object in ASP Net identity  as at this date  is   var user   UserManager FindById User Identity GetUserId       or  if you have an async action  something like   var user   await UserManager FindByIdAsync User Identity GetUserId       FindById requires you have the following using statement so that the non-async UserManager methods are available  they are extension methods for UserManager  so if you do not include this you will only see FindByIdAsync    using Microsoft AspNet Identity    If you are not in a controller at all  e g  you are using IOC injection   then the user id is retrieved in full from   System Web HttpContext Current User Identity GetUserId      If you are not in the standard Account controller you will need to add the following  as an example  to your controller   1  Add these two properties            lt summary gt          Application DB context          lt  summary gt      protected ApplicationDbContext ApplicationDbContext   get  set              lt summary gt          User manager - attached to application DB context          lt  summary gt      protected UserManager lt ApplicationUser gt  UserManager   get  set      2  Add this in the Controller s constructor       this ApplicationDbContext   new ApplicationDbContext        this UserManager   new UserManager lt ApplicationUser gt  new UserStore lt ApplicationUser gt  this ApplicationDbContext      Update March 2015  Note  The most recent update to Identity framework changes one of the underlying classes used for authentication  You can now access it from the Owin Context of the current HttpContent   ApplicationUser user   System Web HttpContext Current GetOwinContext   GetUserManager lt ApplicationUserManager gt    FindById System Web HttpContext Current User Identity GetUserId       Addendum   When using EF and Identity Framework with Azure  over a remote database connection  e g  local host testing to Azure database   you can randomly hit the dreaded    error  19 - Physical connection is not usable     As the cause is buried away inside Identity Framework  where you cannot add retries  or what appears to be a missing  Include x- gt someTable    you need to implement a custom SqlAzureExecutionStrategy in your project

User · Answer

In case someone is working with Identity users in web forms  I got it working by doing so   var manager   Context GetOwinContext   GetUserManager lt ApplicationUserManager gt     var user   manager FindById User Identity GetUserId

User · Answer

As of ASP NET Identity 3 0 0  This has been refactored into    returns the userid claim value if present  otherwise returns null User GetUserId

User · Answer

I was successfully available to get Application User By Following Piece of Code  var manager   new UserManager lt ApplicationUser gt  new UserStore lt ApplicationUser gt  new ApplicationDbContext                  var user   manager FindById User Identity GetUserId                 ApplicationUser EmpUser   user

[c#] ASP.NET MVC 5 - Identity. How to get current ApplicationUser

Examples related to c#

Examples related to asp.net-mvc-5

Examples related to identity

Examples related to asp.net-identity