Replies: 2 comments 2 replies
-
|
I would say this should be standard if tracing is enabled in the Keycloak configuration. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Please create an enhancement issue. Thanks! |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There are multiple cases where a user gets the message "We are sorry... Invalid username or password."
Sometimes this is due to misconfigured authentication flows (see #15439) and sometimes it could really be a user error.
When supporting administrators with their Keycloak configuration, we often end up searching for the root cause of such an error by looking at login events and log entries. However it is hard to find the corresponding entry just by time when the screenshot was taken.
Proposal
It would be very helpful to have Trace ID displayed on error pages which are rendered to the user during login.
This ID should also end up at the login event and at the log entries which correspond to the login process.
Mockup screens
User screen which shows Trace ID

Login events showing Trace ID

Discussion
Is there interest in such a feature to better find the cause of an error during login?
Could this be implemented to work for all Authenticators and all errors which might be displayed during login?
Beta Was this translation helpful? Give feedback.
All reactions