# Show lock out failure for user authenticating with incorrect credentials **URL:** \ **Category:** OAuth/OIDC\ **Tags:** api\ **Created:** [June 5, 2023, 7:06pm UTC](https://devforum.okta.com/t/show-lock-out-failure-for-user-authenticating-with-incorrect-credentials/24456 "2023-06-05T19:06:43Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![vdc305](https://avatars.discourse-cdn.com/v4/letter/v/e19b73/32.png) [@vdc305](https://devforum.okta.com/u/vdc305)\ **Post date:** [June 5, 2023, 7:06pm UTC](https://devforum.okta.com/t/show-lock-out-failure-for-user-authenticating-with-incorrect-credentials/24456/1 "2023-06-05T19:06:43Z")
I am using Okta idx @okta/okta-auth-js version 7.3.0 and Okta’s identity engine. I have the authenticator enrollment password policy checked with “Show lock out failures” and “Lock out user after 5 unsuccessful attempts”. When I try to authenticate a user with incorrect credentials, I get nextSteps with challenge-authenticator and inputs as password. I never get the count or message as to user has been locked out of their account due to too many failed login attempts ---
**Author:** ![erik](https://avatars.discourse-cdn.com/v4/letter/e/b5ac83/32.png) [@erik](https://devforum.okta.com/u/erik)\ **Post date:** [August 21, 2023, 10:53pm UTC](https://devforum.okta.com/t/show-lock-out-failure-for-user-authenticating-with-incorrect-credentials/24456/2 "2023-08-21T22:53:51Z")
Hello, It could be that if you have two password authenticator policies both set to the same group (everyone), and one allows showing the lockout failure and the other does not that you would end up not getting the lockout message returned from the backend. Thank You, ---
**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\ **Post date:** [February 15, 2024, 5:34pm UTC](https://devforum.okta.com/t/show-lock-out-failure-for-user-authenticating-with-incorrect-credentials/24456/3 "2024-02-15T17:34:42Z")