Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include status of OAuth2 service in app and environment status #1045

Closed
nilsgstrabo opened this issue Jun 25, 2024 · 0 comments · Fixed by #1053
Closed

Include status of OAuth2 service in app and environment status #1045

nilsgstrabo opened this issue Jun 25, 2024 · 0 comments · Fixed by #1053
Assignees

Comments

@nilsgstrabo
Copy link
Contributor

nilsgstrabo commented Jun 25, 2024

The app "box" on the front page and the environment "boxes" on the application page aggregates statuses from components and secrets, and if something is not running correclty, an exclamation icon is shown:

image

image

This status is calculated from component replicas, and if any of them are not running correctly, a warning is shown.
The status does not include the OAuth2 service replica statuses, and if this one is failing, e.g. due to incorrect Redis password, there is no indication of a problem in the app list on the front page, or the app's environment page. This makes it hard to debug (follow the signs) for users have not correctly configured the OAuth2 service.

I suggest that we include the OAuth2 service status in the app "box" and environment "boxes". It would also be useful to show the OAuth2 replicas in the active component list, possibly suffixed with "(OAuth2)"

image

DoD

Errors with OAuth service aggregates to the top error icon/report

@nilsgstrabo nilsgstrabo added the refinement needed Refinement needed label Jun 25, 2024
@emirgens emirgens removed the refinement needed Refinement needed label Jun 26, 2024
@nilsgstrabo nilsgstrabo self-assigned this Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants