User's AccessFailedCount field is not reset after successful login
Hi, I've not found such issue in the forum but if it exists, please send me a link and I will close this topic.
I fount that User AccessFailedCount field is not reset after login. I can see that it stays the same in DB.
Steps to reproduce:
1. Try to login with a user using wrong password 2 times of 3 in any browser.
2. Login with the same user successfully using right password.
3. Logout.
4. Try to login with the same user using wrong password 2 times.
5. Try to login using right password and you can't do it cause the failed count field wasn't reset previously.
I found a fix for it. The AccessFailedCount field was updated in DB but not in the BackOfficeIdentityUser reference. So I created custom back office manager and overridden CheckPasswordAsync.
User's AccessFailedCount field is not reset after successful login
Hi, I've not found such issue in the forum but if it exists, please send me a link and I will close this topic.
I fount that User AccessFailedCount field is not reset after login. I can see that it stays the same in DB.
Steps to reproduce: 1. Try to login with a user using wrong password 2 times of 3 in any browser. 2. Login with the same user successfully using right password. 3. Logout. 4. Try to login with the same user using wrong password 2 times. 5. Try to login using right password and you can't do it cause the failed count field wasn't reset previously.
I found a fix for it. The AccessFailedCount field was updated in DB but not in the BackOfficeIdentityUser reference. So I created custom back office manager and overridden CheckPasswordAsync.
Now it works properly.
Could you please answer if it's my bad or it's an issue?
Thank you very much.
Hi Iaroslav
Really good finding, #h5yr!
Can you make a pull request?
Thanks,
Oleksandr
Ok, I will try. It's a fix for my project but I'm not sure where I need to put this code in the project. But anyway reviewers will correct me :)
What version of Umbraco are you using?
7.5.11
Iaroslav, there is no such problem in Umbraco 7.7.7
Ok, great, thank you very much!
You are welcome, have a great day
is working on a reply...