Terraform · Authentication Profile

Terraform Authentication

Authentication

Terraform secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

Infrastructure as CodeCloud InfrastructureDevOpsOpen-SourceHashiCorp
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-06-20'
method: searched
source: openapi/hcp-terraform-openapi.yml
docs: https://developer.hashicorp.com/terraform/cloud-docs/users-teams-organizations/api-tokens
summary:
  types:
  - http
  api_key_in: []
  oauth2_flows: []
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: >-
    Bearer token authentication. HCP Terraform issues three token kinds — user
    tokens (act as a user), team tokens (scoped to a team's permissions), and
    organization tokens (one per org, for org-level automation). Tokens are sent
    as `Authorization: Bearer <token>`. The public Terraform Registry API needs
    no authentication for discovery/download.
  token_types: [user, team, organization]
  header: Authorization
  docs: https://developer.hashicorp.com/terraform/cloud-docs/users-teams-organizations/api-tokens
  sources:
  - openapi/hcp-terraform-openapi.yml
notes: >-
  The Terraform Registry API (registry.terraform.io) is unauthenticated for
  public module/provider read and download. HCP Terraform also acts as an OIDC
  identity provider (well-known/terraform-app-openid-configuration.json) for
  workload identity / dynamic provider credentials — that is token issuance for
  runs, distinct from API authentication.