Vishal Mahajan
Vishal Mahajan
It was meant to be worked upon after the merge :)
As per current implementation, configurable `CORS` settings are applied against following URI patterns in the `WebConfigurer`. If your URL path doesn't match against these patterns, then, the default `CORS` configuration...
You can find their coverage under corresponding `.vue` files like `user-management-edit.vue` contains the coverage of `JhiUserManagementEdit`.
I think it's related to https://github.com/SonarSource/SonarTS/issues/477
The intention was to deny `CORS` by default, and if the user would like to open, then he can override during application startup. However, there is still a problem noted...
I have started on maven part to bump dependencies to latest. I will soon raise a draft PR.
Post upgrade, I don't see an issue with native image build/startup. Can you try latest branch code to see if this works for you as well?
With #247 changes, I tried using `22.2.r17-grl` Graal VM image and didn't observe the issue. You now need to explicitly specify the quarkus profile to use for native image build...
> I solved this issue changing in "realm-config/jhipster-realm.json", the line 29 from "sslRequired": "external" to "sslRequired": "none" It's purposely done to enforce use of SSL for public facing deployments. We...