Vault Learning Resources: Transit Secrets Engine, OpenID Connect Auth Method

We are excited to announce additional hands-on tutorials to help you learn and integrate Vault as your secrets management solution. Several pre-existing tutorials have also been updated.

What's New?


»Auto-Unseal with Transit Secrets Engine

In addition to AliCloud KMS, Amazon KMS, Azure Key Vault, and Google Cloud KMS, Vault 1.1 added support for the Transit Secrets Engine to auto-unseal your Vault.

Auto-unseal

This guide walks you through the steps necessary to configure Transit Auto-Unseal.

If you don't have a Vault environment to experiment with Transit Auto-Unseal, click the Show Terminal button to launch an interactive tutorial in your web browser.

Launch Katacoda

»OpenID Connect (OIDC) Auth Method

Vault clients must first authenticate with Vault to acquire a valid token. Vault 1.1 introduced support for OpenID Connect (OIDC) as an auth method which is provided by many authentication services such as Auth0.

OIDC Auth Method

This guide walks through the configuration of the OIDC auth method using Auth0 as its OIDC provider.

NOTE: Refer to the Vault OpenID Demo for an example using Google OAuth.

»Update: Vault Agent Caching

Vault Agent was first introduced in Vault 0.11 as a client daemon to automate the authentication and token lifecycle management. Vault 1.1 introduced its caching mechanism to further improve the efficiency of token and lease management.

Vault Agent

The Vault Agent Caching tutorial now has a Katacoda scenario to demonstrate both Auto-Auth and Caching of Vault Agent using the approle auth method. If you don't have a Vault environment, try the Katacoda interactive tutorial today!

You can find many other educational resources, demo code, and interactive experiences at HashiCorp Learn or attend a training event with one of our training partners.


Sign up for the latest HashiCorp news

By submitting this form, you acknowledge and agree that HashiCorp will process your personal information in accordance with the Privacy Policy.