-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
False
-
-
False
-
-
Description:
This is an issue found in Quay new UI Login Page, now when login Quay was failed with 500 error page on current UI, found on new UI Quay will display a raw HTTP 500 status code directly to the end-user, that's not good practices, pls review this issue.
The Quay UI should not display a raw HTTP 500 status code directly to the end-user. While technically accurate, it's a poor practice from both a user experience and security standpoint.
An improved error message would look like this:
"Unable to sign in due to an unexpected issue. Please contact support and provide this reference code: a73b1-d9f2c"
Quay PR: https://github.com/quay/quay/pull/4252
Quay Current UI:

Quay new UI:

- account is impacted by
-
PROJQUAY-8710 Quay new UI known issues List
-
- New
-
- links to