FailedPasswordAttempts and default UmbracoMembershipProvider
Hello,
Have encountered some unexpected behaviour using the default UmbracoMembershipProvider
Have implemented my own login surface controller and it is working fine, can log in calling the MembershipHelper.Login()
However when I try with a new member, the Failed Password Attempts property doesn't seem to increment beyond 1
Tried to sign in multiple times with wrong password
I would expect this to increment steadily...
Then logged in using the correct password and this reset the Failed Password Attempts to 0, which is what I would have expected
Then I tired logging in with wrong password and expected, maybe, Failed Password Attempts to increment to 1
But it's now at 2 !
Now if I login with proper password it resets back to 0
But an incorrect login brings it now up to 3!
I log back in it goes to 0, then a failed login brings it back up to 3, and i can't get it to increment any further
Is this all meant to happen/expected behaviour?
This feels a bit like a bug, but I thought to ask a question first before raising, as there may be an explanation for this :)
FailedPasswordAttempts and default UmbracoMembershipProvider
Hello,
Have encountered some unexpected behaviour using the default UmbracoMembershipProvider Have implemented my own login surface controller and it is working fine, can log in calling the MembershipHelper.Login()
However when I try with a new member, the Failed Password Attempts property doesn't seem to increment beyond 1 Tried to sign in multiple times with wrong password I would expect this to increment steadily...
Then logged in using the correct password and this reset the Failed Password Attempts to 0, which is what I would have expected
Then I tired logging in with wrong password and expected, maybe, Failed Password Attempts to increment to 1
But it's now at 2 !
Now if I login with proper password it resets back to 0
But an incorrect login brings it now up to 3!
I log back in it goes to 0, then a failed login brings it back up to 3, and i can't get it to increment any further
Is this all meant to happen/expected behaviour?
This feels a bit like a bug, but I thought to ask a question first before raising, as there may be an explanation for this :)
is working on a reply...