Backport of Passes configured role name to Vault for AWS auth in Connect CA into release/1.16.x #18099
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.
Backport
This PR is auto-generated from #17885 to be assessed for backporting due to the inclusion of the label backport/1.16.
The below text is copied from the body of the original PR.
Fixes #17887.
Description
When using Connect, with Vault CA, with AWS auth - this change ensures that the
role
name (if configured) is passed as part of the login request. Prior to this change, Consul did not respect this parameter and therefore always falls back to the default Vault behaviour of using the instance AWS IAM role name, even ifrole
was specified inparams
.Testing & Reproduction steps
TestVaultCAProvider_AWSLoginDataGenerator
tests.To reproduce original bug
role
is not sent to Vault, Vault will attempt to use the IAM instance role name and fail if this does not exist as a Vault role.Links
https://developer.hashicorp.com/vault/api-docs/auth/aws#login
https://github.com/hashicorp/vault/blob/f381fba4a6468921c4d7d90e04db7bfb9bef4f52/builtin/credential/aws/cli.go#L67
PR Checklist
external facing docs updated(Not applicable)Overview of commits