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
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
Using the archetype 3.0.0 it is not possible to access the h2 console by specifying another context path for the application different to / and providing the properties
Removing all the authorization of the application results in a valid behavior of the h2 console. So it seems, that we have to whitelist /h2 somewhere and maybe properly provide a context path for the application to prevent name clashes in URLs
@jdiazgon thank you so much for your feedback and investigation.
Disabling security features for the sake of accessing some h2 feature is somewhat odd however. We IMHO need at least to find a way how to configure these "disabling" only for the h2 URLs. Still I do not like such tweaks in productive code. Great that you just added it as comment. However, there is a high risk that people using it may accidentally commit such change and break the security. Therefore we still need to find a safer and more elegant way.
Anyhow, thank you very much as you help us to guide the way to the "perfect solution".
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using the archetype 3.0.0 it is not possible to access the h2 console by specifying another context path for the application different to / and providing the properties
Logging into the console always results in a 403 error.
The text was updated successfully, but these errors were encountered: