feat: ability for reverse proxy to enforce own auth scheme #102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A reverse proxy must be used in order to use this application. Since such a proxy might want to enforce it's own authentication mechanism, a small adaption is needed how requests to
jmwalletd
are constructed and forwarded.This change includes sending the bearer token via a header named
x-jm-authorization
instead ofAuthorization
in order for the reverse proxy to use theAuthorization
header for it's own purposes.From this change onward, any reverse proxy that wants to deliver this application must forward the
x-jm-authorization
header asAuthorization
header tojmwalletd
. No other changes are needed for the development environment.