SDK Not returning the right error when account locked.

[cgstaber]

Describe the bug

When a user tries to authenticate with a locked account (from bad password attempts) and enters the correct password, the sdk acts as though they've entered the wrong password and gives no indication anywhere that the account is locked.

I also tested this against the hosted widget and it also shows the same behavior.

Reproduction Steps?

Lock an account by too many bad password attempts. Refresh the page. Enter the correct password. You get the invalid username/password message and not the locked messsage.

SDK Versions

All

Additional Information?

No response

[cgstaber]

This issue is especially frustrating because you don't allow us an endpoint to call to determine if an account is locked other than the rate limited get user api. So we really don't have a way around this to make a better experience for our users.

[pzi]

have you enabled "show lock out failures"?

[cgstaber]

Yes

[cgstaber]

I just noticed this morning that when someone would lock their account, you would get requestDidSucceed: true, but this morning I started getting requestDidSucceed: false.