You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the OIDC code flow fails, then a user can point to to an error handler endpoint with quarkus.oidc.authentication.error-path. Error handler can provide a nicely formatted page, and suggest a user to retry by following some link, etc.
If the error handler is not available, 401 is returned. But it would be better return the error code and description directly to the user as a simple text message. Users can see them in the browser URL but it is not easy
Implementation ideas
Return a text message including the error code and description if no error handler is available
The text was updated successfully, but these errors were encountered:
Description
If the OIDC code flow fails, then a user can point to to an error handler endpoint with
quarkus.oidc.authentication.error-path
. Error handler can provide a nicely formatted page, and suggest a user to retry by following some link, etc.If the error handler is not available, 401 is returned. But it would be better return the error code and description directly to the user as a simple text message. Users can see them in the browser URL but it is not easy
Implementation ideas
Return a text message including the error code and description if no error handler is available
The text was updated successfully, but these errors were encountered: