在asp.net mvc的GenerateUserIdentityAsync使用Ninject添加自定義的要求

Question

我需要添加自定義聲明時，通過執行讀取到數據庫中並添加值（從谷歌外部標誌）的用戶體徵恢復。我正在使用Ninject進行依賴注入，以將控制器注入到我的業務層服務中。

所以我所在的identityModels.cs方法添加索賠：

public async Task<ClaimsIdentity> GenerateUserIdentityAsync(UserManager<ApplicationUser> manager) 
    { 
     // Note the authenticationType must match the one defined in CookieAuthenticationOptions.AuthenticationType 
     var userIdentity = await manager.CreateIdentityAsync(this, DefaultAuthenticationTypes.ApplicationCookie); 
     // Add custom user claims here 

     string userId = userIdentity.GetUserId(); 

     //var _iUserBLL = (IUserBLL)System.Web.Mvc.DependencyResolver.Current.GetService(typeof(IUserBLL)); 
     //UserBO objUser = _iUserBLL.GetById(userId); 

     //userIdentity.AddClaim(new Claim("Value1", objUser.Value1)); 
     //userIdentity.AddClaim(new Claim("Value2", objUser.Value2)); 
     return userIdentity; 
    } 

這裏System.Web.Mvc.DependencyResolver.Current.GetService線失敗，並導致其崩潰。這在其他地方工作，我也試過我用注入控制器像相同的方法：

public class MyController : Controller 
{ 
    private readonly IUserBLL _iUserBLL; 

    public MyController (IUserBLL iUserBLL) 
    { 
     _iUserBLL = iUserBLL; 
    } 
} 

甚至：

[Inject] 
    public IUserBLL _iUserBLL { get; set; } 

但在GenerateUserIdentityAsync方法使用時_iUserBLL爲空。任何想法如何我可以注入我的IUserBLL在這裏進行自定義數據庫調用？

多一點信息 - 如果你不熟悉這種方法，它與個人用戶帳戶Visual Studio項目生成的身份代碼的一部分。

類的全是像這樣：

public class ApplicationUser : IdentityUser 
{ 
    public async Task<ClaimsIdentity> 
     GenerateUserIdentityAsync(UserManager<ApplicationUser> manager) 
    { 
     ... 
    } 
} 

於是，我就在這裏構造函數，它不工作：

public class ApplicationUser : IdentityUser 
    { 
     private readonly IUserBLL _iUserBLL; 

     public ApplicationUser (IUserBLL iUserBLL) 
     { 
      _iUserBLL = iUserBLL; 
     } 
... 
} 

的IdentityUser在前期的內部運作聲明提供identity.entityframework類，並從我不能編輯的內部調用，所以我很困惑如何處理這個？您的回覆薩姆

感謝，它把我拉到一個解決方案。這是我結束的代碼。我遇到了靜態的'Create'方法，所以我改用了[Inject]屬性。有沒有辦法改變靜態的'Create'方法在構造函數中使用IUserBLL？下面是我使用的代碼：

在App_Start/IdentityConfig.cs

// Configure the application sign-in manager which is used in this application. 
    public class ApplicationSignInManager : SignInManager<ApplicationUser, string> 
    { 
     [Inject] 
     public IUserBLL _iUserBLL { get; set; } 

     public ApplicationSignInManager(ApplicationUserManager userManager, IAuthenticationManager authenticationManager) 
      : base(userManager, authenticationManager) 
     { 
     } 

     public override Task<ClaimsIdentity> CreateUserIdentityAsync(ApplicationUser user) 
     { 

      var userIdentity = user.GenerateUserIdentityAsync((ApplicationUserManager)UserManager); 

      UserBO objUser = _iUserBLL.GetById(user.Id); 

      userIdentity.Result.AddClaim(new Claim("Claim1", objUser.Value1)); 
      userIdentity.Result.AddClaim(new Claim("Claim2", objUser.Value2)); 

      return userIdentity; 

     } 

     public static ApplicationSignInManager Create(IdentityFactoryOptions<ApplicationSignInManager> options, IOwinContext context) 
     { 
      return new ApplicationSignInManager(context.GetUserManager<ApplicationUserManager>(), context.Authentication); 
     } 
    } 

在我NinjectWebCommon.cs我還包括這些行，多餘的我所有的綁定：

private static void RegisterServices(IKernel kernel) 
     { 
kernel.Bind<System.Security.Principal.IPrincipal>().ToMethod(context => HttpContext.Current.User).InRequestScope(); 
      kernel.Bind<ApplicationUserManager>().ToMethod(context => HttpContext.Current.GetOwinContext().GetUserManager<ApplicationUserManager>()).InRequestScope(); 
      kernel.Bind<ApplicationSignInManager>().ToMethod((context) => 
      { 
       var cbase = new HttpContextWrapper(HttpContext.Current); 
       return cbase.GetOwinContext().Get<ApplicationSignInManager>(); 
      }); 
... 
} 

Answer 1

ApplicationUser是實體對象和這種對象是負責保持數據不這樣做的邏輯。如果您在UserManager而不是ApplicationUser添加自定義的要求它會好很多。試想一下：

public class ApplicationUserManager: UserManager<ApplicationUser> 
{ 
    private readonly IUserBLL _iUserBLL; 

    public ApplicationSignInManager(IUserStore<ApplicationUser> store, 
     IUserBLL iUserBLL) 
     : base(store) 
    { 
     // if you already fully integrated Identity with ninject, 
     // ninject could automatically resolve this for you. 
     _iUserBLL=iUserBLL; 
     // other configurations here 
    } 

    public override async Task<ClaimsIdentity> CreateIdentityAsync(
     ApplicationUser user, 
     string authenticationType)   
    { 
     var userIdentity=await base.CreateIdentityAsync(user, authenticationType); 
     UserBO objUser = _iUserBLL.GetById(userId); 

     userIdentity.AddClaim(new Claim("Value1", objUser.Value1)); 
     userIdentity.AddClaim(new Claim("Value2", objUser.Value2)); 

     return userIdentity; 
    } 
}