我一直在学习开箱即用的
Owin Identity,我喜欢它为我们提供用户管理的易用性.然后我遇到的问题是它通过ApplicationDbContext直接与EF(貌似)进行交互,这是我不想要的.我更喜欢使用我的3层架构,IE它与服务层(BLL)交互,后者与EF交互.我找不到模板,教程,甚至起点来维护所提供的所有功能并实现我想要的分离.
那么有没有办法在MVC Identity包中使用服务层代替ApplicationDbContext.
最佳答案 如果要使用现有数据库/表,则不必使用整个ASP.Net标识.相反,您可以使用Owin Cookie身份验证中间件.
我在GitHub处有示例代码.如果要测试它,只需在AccountController.cs设置一个断点,然后返回true.
以下是配置中间件和登录的两个主要类别.
public class Startup
{
public void Configuration(IAppBuilder app)
{
app.UseCookieAuthentication(new CookieAuthenticationOptions
{
AuthenticationType = "ApplicationCookie",
LoginPath = new PathString("/Account/Login")
});
}
}
public class OwinAuthenticationService : IAuthenticationService
{
private readonly HttpContextBase _context;
private const string AuthenticationType = "ApplicationCookie";
public OwinAuthenticationService(HttpContextBase context)
{
_context = context;
}
public void SignIn(User user)
{
IList<Claim> claims = new List<Claim>
{
new Claim(ClaimTypes.Name, user.UserName),
new Claim(ClaimTypes.GivenName, user.FirstName),
new Claim(ClaimTypes.Surname, user.LastName),
};
ClaimsIdentity identity = new ClaimsIdentity(claims, AuthenticationType);
IOwinContext context = _context.Request.GetOwinContext();
IAuthenticationManager authenticationManager = context.Authentication;
authenticationManager.SignIn(identity);
}
public void SignOut()
{
IOwinContext context = _context.Request.GetOwinContext();
IAuthenticationManager authenticationManager = context.Authentication;
authenticationManager.SignOut(AuthenticationType);
}
}