# Getting precise login error and displaying it in Sign In Widget

**URL:** <https://devforum.okta.com/t/getting-precise-login-error-and-displaying-it-in-sign-in-widget/25534>\
**Category:** Questions\
**Created:** [October 10, 2023, 2:51pm UTC](https://devforum.okta.com/t/getting-precise-login-error-and-displaying-it-in-sign-in-widget/25534 "2023-10-10T14:51:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcarrollcybersove](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@jcarrollcybersove](https://devforum.okta.com/u/jcarrollcybersove)\
**Post date:** [October 10, 2023, 2:51pm UTC](https://devforum.okta.com/t/getting-precise-login-error-and-displaying-it-in-sign-in-widget/25534/1 "2023-10-10T14:51:15Z")

</div>

Tenant is OIE. We have a policy that will deny a user if a certain attribute is found on the user profile. We are able to capture the fact that an error occurred and can update the Sign-in widget with a custom message. The problem that we have is that we are trying to capture the precise error by code so that we can let the use know the best next step. For instance, there is an Error 0000057 in particular we would like to handle in a special way,

Any insights or pointers to resolve, research, etc will be greatly appreciated.

---

<div class="post-metadata">

**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, 11:59pm UTC](https://devforum.okta.com/t/getting-precise-login-error-and-displaying-it-in-sign-in-widget/25534/2 "2024-02-15T23:59:04Z")

</div>

Closed on February 15, 2024, 11:59pm UTC