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
When attempting to create a project level role bindings with the roles/servicemanagement.serviceConsumer role, the GCP secrets backend returns the following error:
could not write to vault Error making API request.
URL: PUT https:/<vaullt_server>/v1/gcp/roleset/<roleset_name>
Code: 400. Errors:
* unable to set policy: googleapi: Error 400: Role (roles/servicemanagement.serviceConsumer) does not exist in the resource's hierarchy.
When attempting to create a project level role bindings with the
roles/servicemanagement.serviceConsumer
role, the GCP secrets backend returns the following error:Roleset binding:
This error indicates that the
roles/servicemanagement.serviceConsumer
cannot be set in the project IAM policy.The error in StackDriver when the
SetIamPolicy
method is invoked results in an invalid argument error.The binding successfully is applied to the Vault managed service account manually and indicates the role is supported for project level bindings.
The text was updated successfully, but these errors were encountered: