The vite dev server is not capable of handling authorization with KeyCloak (even not when proxying).
This means the developer has to navigate to the URL of the API-Gateway to get a valid SSO session and then return to the Vite dev server to start developing.
Desired solution
The problem can be improved by providing the user with a custom alert with the missing SSO session through the Vite proxy. This alert should then be able to open a new tab automatically to have the developer get a SSO session.
Considered alternatives (optional)
Additional context (optional)
No response
No duplicate
[X] I confirm that this issue is not a duplicate
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Relevant template
refarch-frontend
Problem description (optional)
The vite dev server is not capable of handling authorization with KeyCloak (even not when proxying). This means the developer has to navigate to the URL of the API-Gateway to get a valid SSO session and then return to the Vite dev server to start developing.
Desired solution
The problem can be improved by providing the user with a custom alert with the missing SSO session through the Vite proxy. This alert should then be able to open a new tab automatically to have the developer get a SSO session.
Considered alternatives (optional)
Additional context (optional)
No response
No duplicate
Code of Conduct