mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-12-07 12:35:36 +00:00
a43e292424
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Vault Agent Auto-Auth GCP Method"
|
|
sidebar_title: "GCP"
|
|
sidebar_current: "docs-agent-autoauth-methods-gcp"
|
|
description: |-
|
|
GCP Method for Vault Agent Auto-Auth
|
|
---
|
|
|
|
# Vault Agent Auto-Auth GCP Method
|
|
|
|
The `gcp` method performs authentication against the [GCP Auth
|
|
method](https://www.vaultproject.io/docs/auth/gcp.html). Both `gce` and `iam`
|
|
authentication types are supported.
|
|
|
|
## Credentials
|
|
|
|
Vault will use the GCP SDK's normal credential chain behavior. You can set a
|
|
static `credentials` value but it is usually not needed. If running on GCE
|
|
using Application Default Credentials, you may need to specify the service
|
|
account and project since ADC does not provide metadata used to automatically
|
|
determine these.
|
|
|
|
## Configuration
|
|
|
|
- `type` `(string: required)` - The type of authentication; must be `gce` or `iam`
|
|
|
|
- `role` `(string: required)` - The role to authenticate against on Vault
|
|
|
|
- `credentials` `(string: optional)` - When using static credentials, the
|
|
contents of the JSON credentials file
|
|
|
|
- `service_account` `(string: optional)` - The service account to use, if it
|
|
cannot be automatically determined
|
|
|
|
- `project` `(string: optional)` - The project to use, if it cannot be
|
|
automatically determined
|
|
|
|
- `jwt_exp` `(string or int: optional)` - The number of minutes a generated JWT
|
|
should be valid for when using the `iam` method; defaults to 15 minutes
|