Skip to content
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

Closed
patbaumgartner opened this issue Apr 27, 2020 · 4 comments
Closed

Redirect ignores Alpine -context parameter #665

patbaumgartner opened this issue Apr 27, 2020 · 4 comments
Assignees
Labels
defect Something isn't working p2 Non-critical bugs, and features that help organizations to identify and reduce risk pending release
Milestone

Comments

@patbaumgartner
Copy link

patbaumgartner commented Apr 27, 2020

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:

java $JAVA_OPTIONS -DdependencyTrack.logging.level=$LOGGING_LEVEL -jar dependency-track-embedded.war -context /dtrack

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:

  • Dependency-Track Version: 3.8
  • Distribution: Executable WAR
  • Browser: Chrome

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.

@stevespringett stevespringett added defect Something isn't working and removed in triage labels Apr 27, 2020
@stevespringett
Copy link
Member

stevespringett commented Apr 27, 2020

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.

@patbaumgartner
Copy link
Author

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.

@stevespringett
Copy link
Member

Closing. Fixed in v4.0 - to be released soon.

@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
defect Something isn't working p2 Non-critical bugs, and features that help organizations to identify and reduce risk pending release
Projects
None yet
Development

No branches or pull requests

2 participants