Ability to Add an Authentication Header for External REST API Authentication #1759
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.
Dear @tchiotludo,
Thank you for your time on still maintaining and improving this project and very excited for the upcoming release.
I have added a draft where it will allow users that are using the external REST authentication method to add a single authentication header while they are doing their requests.
This might become useful, at least in our case is, where the external authentication API is also exposed to the internet, and the user wants to limit this access just through a static token that is passed through the service.
This draft implements this functionality in the most basic form with the ability to add a single header to the request.
I would kindly request you to inform me back and what I can improve if you find this feature also a feasible thing to add to the next release.