Open blivonnen opened 9 months ago
I am having the same issue, but on spring session timeout. Can we modify keycloak's security defenses to allow this?
@divukman You should be able to modify your local Keycloak instance to test a solution. If you figure out what works, please let us know how you fixed it.
Locally I am unable to get the CSP error, not sure why. But, I am getting different behavior. After spring session timeout, if any request is made from the app, it goes to login oidc page, which returns 302 to keycloak login. Since its ajax request, keycloak just says CORS error and we are stuck on the UI until we refresh whole web page (which shows keycloak login). Is this something that is expected or some misconfiguration on my part? (I thought there would be axios interceptor for 302's or something).
Overview of the issue
When a user is not logged in the following message appears:
Motivation for or Use Case
I assume this call shouldn't fail or shouldn't be done
Reproduce the error
Fresh generation: Gateway, oauth2 Keycloak, react Services launched in Docker: docker-compose -f src/main/docker/services.yml up -d
Jhipster v8.0.0 tested on Safari, Chrome, Postman (MacOS)
JHipster configuration
JDL definitions