asp.net-identity

1) Create new MVC app targeting 4.6.1 (not core, using MSVS 2015 Update 3) 2) In the generated class ApplicationUser.cs add an assertion: public async Task<ClaimsIdentity> GenerateUserIdentityAsync(UserManager<ApplicationUser> manager) { HttpContext httpContext = HttpContext.Current; Debug.Assert(httpContext != null); // assertion fails // ... } 3) Run program in the debugger, login, the assertion fires. This workaround fixes the problem however I was told that HttpContext should be available across async/await as of .NET 4.5. Should I need the workaround? Web.Config: <httpRuntime

I'm using Asp.Net Identity 2.0, configured so that the users' email address is also the username, so in IdentityConfig I have set AllowOnlyAlphanumericUserNames = false in the ApplicationUserManager constructor: public class ApplicationUserManager : UserManager<ApplicationUser> { public ApplicationUserManager(IUserStore<ApplicationUser> store) : base(store) { } public static ApplicationUserManager Create(IdentityFactoryOptions<ApplicationUserManager> options, IOwinContext context) { var manager = new ApplicationUserManager(new UserStore<ApplicationUser>(context.Get<ApplicationDbContext>())); /

I have been following this post on creating a custom "storage provider" for the new ASP.NET Identity system, and so far it has proven very informative; Creating a custom MySQL Identity Provider I am not using MySQL, I am using RavenDB - and yes, I have already looked at the available RavenDB Identity Providers out there - that isn't really my issue. My issue comes with the IUserRoleStore<IdentityUser> and then the IdentityRole , as well as RoleStore . I see them get created - I even see how they access data to see if a user is in a role, etc. But then later, I just see this .. [Authorize(Roles

So I've been trying to setup ASP.NET Identity 2.2.1 and I keep hitting roadblocks. For being something that is supposed to be auto-generated by the framework it sure seems complicated to configure. I think I'm almost there but I'm still having issues setting up IoC with Simple Injector. I've been reading through other StackOverflow questions and blogs about these issues. Most of them seem out of date because they deal with ASP.NET Identity 1.0. There's even been enough changes from 2.0 to 2.2.1 I've run into some issues with out of date solutions. Or the solutions deal with other IoC

When a user goes to my site they get the login page. Once they successfully login they can logoff and a different user can login. However, if the user clicks the back button while logged in it goes to the login page. At this point a new user can no longer login. I receive an anti-forgery token error. I have tried to logoff any user that goes to the login page. I have tried different ways to logoff. I even tried to Session.Abandon(); Account controller: // GET: /Account/Login [AllowAnonymous] public ActionResult Login(string returnUrl) { EnsureLoggedOut(); ViewBag.ReturnUrl = returnUrl; //