fix(front): add bearer token in racksdb request #477
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add missing bearer token in RacksDB infrastructure diagram request, it is now required by @check_jwt decorator on the gateway endpoint with RFL >= 1.3.0 to avoid HTTP/403 response. The token is removed from request headers for login (incl. anonymous) and login service message at the same time, as the client does not have JWT at this stage yet and the gateway does not enforce the presence of the bearer token for the corresponding endpoints. fix #471
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Add missing bearer token in RacksDB infrastructure diagram request, it is now required by @check_jwt decorator on the gateway endpoint with RFL >= 1.3.0 to avoid HTTP/403 response.
The token is removed from request headers for login (incl. anonymous) and login service message at the same time, as the client does not have JWT at this stage yet and the gateway does not enforce the presence of the bearer token for the corresponding endpoints.
fix #471