asp.net-identity

I am currently trying to reconfigure StructureMap in our application after upgrading from an old version (2.6) that was never correctly implemented in the first place. I am new to using DI Containers to begin with, and am finding documentation for newer StructureMap versions hard to find. I uninstalled the old 2.6 version of StructureMap and installed StructureMap.MVC5 (since I am using MVC5). What I am having issues with is the AccountController. I have StructureMap set up to use the parameterless constructor, but when my application tries to create the UserManager, I get an

I have created Empty MVC (ASP.NET Web Application) project using Visual Studio 2013 Update 2 RC & then added AspNet Identity Samples using: PM>Install-Package Microsoft.AspNet.Identity.Samples -Pre I have enabled and added migrations & then updated database, which created default tables. I want to create Customer table which contains 2 columns as Foreign Keys to: Groups table (GroupId column) AspNetUsers table (Id column) So I have created 2 classes Customer & Group and added Foreign Keys using Data-annotations as shown below: namespace IdentitySample.Models { // You can add profile data for

I would like to know how to properly handle the fact that the cookie expired? Is it possible to execute a custom action ? What I would like to achieve is that when the cookie is expired is to take few informations out of the current cookie at redirect to a action parametrise by this information. Is it possible ? Looks like you need your own handler for OnValidatePrincipal event when setuping cokies auth middleware: OnValidatePrincipal event can be used to intercept and override validation of the cookie identity app.UseCookieAuthentication(options => { options.Events = new

I'm trying to create an MVC5 application that uses Windows Authentication but uses roles pulled from a User model. I've searched high and low for an example, but the only ones I can find are based on the old ASP.NET identity framework. Anyone care to point me in the right direction?! Thanks! So I've figured out one approach to solving this problem. I created a custom Authorization Attribute that checks the User model for a role. using System.Linq; using System.Web; using System.Web.Mvc; using App.Models; using System.Security.Claims; namespace App.Extensions.Attributes { public class

I am using ASPNet Identity to implement security in my web application. There is a requirements where in, I need to extend the IdentityRole and IdentityUser. Here is my code to extend the IdentityUser. public class ApplicationUser : IdentityUser { public virtual User User { get; set; } } public class ApplicationDbContext : IdentityDbContext<ApplicationUser> { public ApplicationDbContext() : base("name=CoreContext") { } protected override void OnModelCreating(DbModelBuilder modelBuilder) { base.OnModelCreating(modelBuilder); modelBuilder.Entity<IdentityUser>() .ToTable("AspNetUsers");