请问asp.net 2.0身份密码散列不同于1.0吗？ [英] Does asp.net identity 2.0 hash passwords differently than 1.0?

问题描述

我刚刚更新从asp.net认同我的应用程序1.0到2.0采取电子邮件确认，双因素身份验证，等等...

I just updated my app from asp.net identity 1.0 to 2.0 to take advantage of the email confirmation, two-factor auth, etc...

不过，用户现在不能登录。这似乎等待UserManager.FindAsync（model.UserName，model.Password）; 没有找到现有谁身份1.0签约用户......但用户的过程中谁签约身份2.0做工精细。

However, user's cannot log in now. It seems await UserManager.FindAsync(model.UserName, model.Password); doesn't find existing users who signed up on identity 1.0... but user's who signed up during identity 2.0 work fine.

推荐答案

散列是完全一样的。

身份2.0 UserManager.FindAsync（用户名，密码）可用于标识1.0注册用户返回null。
有在 AspNetUsers 表中的某些新领域这是必需 - NOT NULL
。
最有可能的原因是 AccessFailedCount 字段。如果为null，你看不到任何异常，只有空用户。

Hashing is exactly the same.
Identity 2.0 UserManager.FindAsync(UserName, Password) can return null for users registered with Identity 1.0. There are some new fields in the AspNetUsers table which are manadatory - NOT NULL.
Most possible reason is the AccessFailedCount field. If it is null, you don't see any exceptions, only null user.

这篇关于请问asp.net 2.0身份密码散列不同于1.0吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！