We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HashiCorp's docs recommend that the IAM auth method be configured to use a nonce (X-Vault-AWS-IAM-Server-ID).
In addition, when the role name in Vault is different from the IAM role, the role name must be specified as well.
This plugin does not allow either values to be configured.
To be clear: as per HashiCorp's docs, a client that authenticates using the IAM method on the CLI would do something like the following:
vault login -method=aws header_value=vault.example.com role=dev-role-iam
This plugin needs to allow for the equivalent of the header_value and role above to be specified.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
HashiCorp's docs recommend that the IAM auth method be configured to use a nonce (X-Vault-AWS-IAM-Server-ID).
In addition, when the role name in Vault is different from the IAM role, the role name must be specified as well.
This plugin does not allow either values to be configured.
To be clear: as per HashiCorp's docs, a client that authenticates using the IAM method on the CLI would do something like the following:
This plugin needs to allow for the equivalent of the header_value and role above to be specified.
The text was updated successfully, but these errors were encountered: