You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While configuring the vault_jwt_auth_backend_role we noticed a slightly odd behavior with the bound_claims parameter when our value contains a ,. With a , in our value the value get's split into a list of strings, which isn't the desired behaviour.
The documentation states that the bound_claims can be either a map with values of string or list of strings.
bound_claims - (Optional) If set, a map of claims/values to match against. The expected value may be a single string or a list of strings.
I would like to help on this issue. But I'm unsure what's the best way to fix the bug.
the bound_claims value could be implemented as stated by the documentation to accept both strings and list of strings
an escape sequence could be specified for the comma separation.
Hi there,
While configuring the
vault_jwt_auth_backend_role
we noticed a slightly odd behavior with thebound_claims
parameter when our value contains a,
. With a,
in our value the value get's split into a list of strings, which isn't the desired behaviour.The documentation states that the
bound_claims
can be either a map with values of string or list of strings.I would like to help on this issue. But I'm unsure what's the best way to fix the bug.
bound_claims
value could be implemented as stated by the documentation to accept both strings and list of stringsTerraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
The configuration for the
example
role should look as follows.Actual Behavior
The claim value get's split at the
,
Important Factoids
terraform-provider-vault/vault/resource_jwt_auth_backend_role.go
Lines 544 to 552 in 3a348ea
References
The text was updated successfully, but these errors were encountered: