Course contentsShow
← Cloud and Infrastructure
Lesson 2256 of 2,98948. Secrets ManagementFree lesson

Vault Authentication Methods Overview

Survey of auth methods including tokens, userpass, AppRole, and cloud provider authentication.

Vault Authentication Methods Overview

What you'll learn: How Vault offers multiple authentication methods so applications, users, and machines can securely prove their identity before accessing secrets.

Now that you've initialized and unsealed your Vault instance, you need a way to control who (or what) can access it. Vault doesn't just hand out secrets to anyone—clients must first authenticate using one of several built-in auth methods.

Core Concept

Think of authentication methods as different types of keys to enter a building. Some people use keycards (tokens), others use passwords (userpass), some use department-issued badges (AppRole), and executives might have biometric scanners (cloud provider identity). All grant access, but each suits different use cases.

Vault supports multiple authentication methods simultaneously:

  • Tokens: The fundamental auth method. Every successful authentication generates a token that grants access. You can also create tokens directly for testing or automation.

  • Userpass: Username and password authentication for human users. Simple but useful for operators and administrators needing interactive access.

  • AppRole: Designed for machines and applications. Uses a role ID (public identifier) and secret ID (credential) combination—perfect for CI/CD pipelines and services.

  • Cloud Provider Auth: AWS IAM, Azure Managed Identity, and GCP Service Accounts can authenticate directly. Your EC2 instance or Kubernetes pod proves its identity using its native cloud credentials—no static secrets needed.

Each method is mounted at a specific path (like /auth/userpass or /auth/aws) and can be configured with policies determining what authenticated clients can access. You enable only the methods your organization needs.

Key Takeaway: Vault's flexible authentication system lets you choose the right identity verification method for each client type—humans use userpass, applications use AppRole, and cloud workloads use native provider authentication.