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
The swagger endpoint simplifies reproducing this.
Log out from any dev deplyoment, go to the swagger page (<URL>/swagger) and authorize with pkce. Then try to invoke any API on the core service.
Other info
Handling that case properly may require changing the UI server as well to add the headers marking the response as "auth-invalid". That will automatically trigger a re-login in the UI client
The text was updated successfully, but these errors were encountered:
Description
It may happen that users have a valid KeyCloak authentication token but no backend tokens.
This happened recently in a couple of cases:
/api/login
The Gateway triggers an exception and the APIs invoked respond with a 500 error. Details in Sentry:
Reproduce
The swagger endpoint simplifies reproducing this.
Log out from any dev deplyoment, go to the swagger page (
<URL>/swagger
) and authorize with pkce. Then try to invoke any API on the core service.Other info
Handling that case properly may require changing the UI server as well to add the headers marking the response as "auth-invalid". That will automatically trigger a re-login in the UI client
The text was updated successfully, but these errors were encountered: