Keycloak error page

[yonas-seyoum]

No description provided.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[peterrogov]

Good start. But this is too narrow.

1. We only use the previous problem with keycloak as an example. The code we make here must handle any (!) error that might occur in the app and go unhandled. Any unhandled exception anywhere.

2. You might really want to consider using ErrorBoundary for this. Read about it.

3. An error occurred during keycloak initialization is a bad idea. Do not allow your user-facing error message to leak any significant implementation details about the app. This violates security very much. You want your logs, that are only visible to admins, to have every neccessary details. But user facing messages must be user facing. In this case just "Service temporary unavailable" or at most "Due to a technical problem we cannot authenticate you right now". That's it.