Search the latest docs

Showing 1-10 of 38 results

Filter by

Search the archives

  • Install Vault with a cluster management project

    Use GitLab › Manage your infrastructure › Connect Kubernetes clusters › Use GitLab CI/CD

    Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed, GitLab Dedicated HashiCorp Vault is a secrets management solution which can be used to safely manage and store passwords ...

  • Vault authentication with GitLab OpenID Connect

    Administer › Authentication and authorization

    Tier : Free, Premium, Ultimate Offering : GitLab Self-Managed, GitLab Dedicated Vault is a secrets management application offered by HashiCorp. It allows you to store and manage sensitive information ...

  • Use HashiCorp Vault secrets in GitLab CI/CD

    Use GitLab › Use CI/CD to build your application › Pipeline security

    to authenticate with HashiCorp Vault instead, as demonstrated on this page. Starting in Vault 1.17, JWT auth login requires bound audiences on the role when the JWT contains an aud claim. The aud claim can ...

  • Use Azure Key Vault secrets in GitLab CI/CD

    Use GitLab › Use CI/CD to build your application › Pipeline security

    . Issue 424746 resolved and this feature made generally available in GitLab Runner 16.6. You can use secrets stored in the Azure Key Vault in your GitLab CI/CD pipelines. Prerequisites: Have a Key Vault ...

  • Tutorial: Update HashiCorp Vault configuration to use ID Tokens

    Use GitLab › Use CI/CD to build your application › Pipeline security › Connect to cloud services

    Tier : Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed, GitLab Dedicated Starting in Vault 1.17, JWT auth login requires bound audiences on the role when the JWT contains an aud claim ...

  • Using external secrets in CI

    Use GitLab › Use CI/CD to build your application › Pipeline security

    required by a job. Read GitLab CI/CD pipeline configuration reference for more information about the syntax. GitLab provides support for the following secret management providers: Vault by HashiCorp ...

  • Connect to cloud services

    Use GitLab › Use CI/CD to build your application › Pipeline security

    Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed, GitLab Dedicated History ID tokens to support any OIDC provider, including HashiCorp Vault, introduced in GitLab 15.7 ...

  • Hardening - CI/CD Recommendations

    Administer › Secure GitLab › Hardening

    should be used, such as GCP Secret Manager, AWS KMS, or HashiCorp Vault. For self-managed and standalone instances, HashiCorp Vault is recommended, and many GitLab features can take advantage of Vault ...

  • OpenID Connect (OIDC) Authentication Using ID Tokens

    Use GitLab › Use CI/CD to build your application › Pipeline security

    to authenticate with HashiCorp Vault. ID tokens are configured in the .gitlab-ci.yml . For example: job_with_id_tokens : id_tokens : FIRST_ID_TOKEN : aud : https://first.service.com SECOND_ID_TOKEN ...

  • Pipeline security

    Use GitLab › Use CI/CD to build your application

    in a secrets manager. When using a secrets manager solution, secrets are stored outside of the GitLab instance. There are a number of providers in this space, including HashiCorp’s Vault , Azure Key ...