Support constructing JwtAuthenticator with token includes Bearer prefix #1949
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.
Support constructing JwtAuthenticator with token includes Bearer prefix
Description
This pull request have made to handle scenario of constructing the JwtAuthenticator with token string which includes the Bearer Prefix. For example, Sending http request from one web service to another which use the same jwt secret. In this scenario it is likable to use the Authorization header value from the original request (to the first service). This value includes the Bearer prefix.
Current Behavior: When Passing the value of the existing Authorization attribute to the JwtAuthenticator constructor the result value of the Authorization attribute of the new request will be "Bearer Bearer "
Expected Behavior: The Authorization header value of the new request will be "Bearer "
Purpose
This pull request is a:
Checklist