AWS SigV4 Auth support #546
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
|
Thank you so much @bmrodgers148 for this huge effort to bring AWS v4 Support to Bruno! ❤️ Merged ! |
|
Hi, |
|
@mirkogolze I'll try to add support to the CLI this week |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding support for AWS Sigv4 auth at request or collection level. Under the hood, it uses awsv4-axios to add an interceptor to the axios instance to sign the requests. Necessary additions have been made for the configuration to be made in the .bru files. No CLI support yet.
To use, just select AWS Sig V4 in the auth mode dropdown menu and enter details.
Service and Region fields are required. If Profile Name is provided, bruno will pull the credentials from the local aws credentials or config .ini files, and will ignore Access Key ID, Secret Access Key, and Session Token, as these values will be pulled from the local AWS envionment.
If there is no profile configured in the .ini files for AWS, profile name should be left blank, and Access Key ID, Secret Access Key, and optionally Session Token should be provided.