-
-
Notifications
You must be signed in to change notification settings - Fork 583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redirect ignores Alpine -context parameter #665
Comments
This is a known limitation of the UI at the moment. The context works for the server's APIs, but not the UI at this time. If you need more control over UI context and other things (TLS, etc), you can optionally deploy the UI independently of the server. |
Thank you so much for your super fast feedback. DT is deployed behind an NGINX with several other apps. Not sure if I want to face other issues when using the frontend and another backend deployment. Probably it's better to wait a bit more. Not sure how I can contribute to that issue. |
Closing. Fixed in v4.0 - to be released soon. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Current Behavior:
Having the Alpine parameter set on the Commandline -context /dtrack in the previous version of DT and now migrating to 3.8 leads to a redirect to /login without taking the context-path into account.
Steps to Reproduce:
Expected Behavior:
I would expect that -context is taken into account when redirects are made. This seems to be a regression because we had previously also problems with the -context parameter.
Environment:
Additional Information:
Running it locally (java -jar dependency-track-embedded.war -context=/dtrack) shows that the -context path is totally ignored. Everything is directly served via / like /dashboards /projects /licenses and so on.
This might be a regression that came in with Alpine 1.8.0-SNAPSHOT.
The text was updated successfully, but these errors were encountered: