9 docs tagged with "Vault"

OIDC/JWT

An auth role is a configuration entity that defines the authentication behavior and permissions associated with a specific category or group of users. An auth role determines how users authenticate and the level of access they have within Vault.

For this example we will use Bash

Create ID Token in Gitlab pipeline

Clone Docker Toolkit (Optional)

Clone Docker Toolkit (Optional)

A mount refers to the process of enabling and configuring a secrets engine within Vault. A secrets engine is a module responsible for generating, managing, and accessing secrets securely.

A policy in Vault is a JSON document that specifies the permissions and capabilities associated with a specific path or set of paths within Vault's hierarchical key-value store. It defines which operations, such as read, write, delete, or list, can be performed on specific paths and the conditions under which those actions are allowed.

We are going to focus on a Docker Single Node Install.