[auth/gcp] Add missing permission to documentation (#8689)
* [auth/gcp] Add missing permission to documentation Signed-off-by: Yong Wen Chua <lawliet89@users.noreply.github.com> * Clarified group aliases
This commit is contained in:
parent
405fbaface
commit
f0720205c3
|
@ -177,6 +177,9 @@ These allow Vault to:
|
||||||
- compare bound fields for GCE roles (zone/region, labels, or membership
|
- compare bound fields for GCE roles (zone/region, labels, or membership
|
||||||
in given instance groups)
|
in given instance groups)
|
||||||
|
|
||||||
|
If you are using Group Aliases as described below, you will also need to add the
|
||||||
|
`resourcemanager.projects.get` permission.
|
||||||
|
|
||||||
#### Permissions For Authenticating Against Vault
|
#### Permissions For Authenticating Against Vault
|
||||||
|
|
||||||
Note that the previously mentioned permissions are given to the _Vault servers_.
|
Note that the previously mentioned permissions are given to the _Vault servers_.
|
||||||
|
@ -204,6 +207,9 @@ will include the following aliases:
|
||||||
]
|
]
|
||||||
```
|
```
|
||||||
|
|
||||||
|
If you are using a custom role for Vault server, you will need to add the
|
||||||
|
`resourcemanager.projects.get` permission to your custom role.
|
||||||
|
|
||||||
## Implementation Details
|
## Implementation Details
|
||||||
|
|
||||||
This section describes the implementation details for how Vault communicates
|
This section describes the implementation details for how Vault communicates
|
||||||
|
|
Loading…
Reference in a new issue