Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • iam_oauth_client
          • iam_oauth_client_secret
          • iam_service_account
          • iam_service_account_api_key
          • iam_service_account_iam_binding
          • iam_service_account_iam_member
          • iam_service_account_iam_policy
          • iam_service_account_key
          • iam_service_account_static_access_key
          • iam_workload_identity_federated_credential
          • iam_workload_identity_oidc_federation
          • iam_workload_identity_oidc_federation_iam_binding

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for output_to_lockbox
  • Import
  1. Terraform reference
  2. Resources
  3. Identity and Access Management (IAM)
  4. Resources
  5. iam_oauth_client_secret

yandex_iam_oauth_client_secret (Resource)

Written by
Yandex Cloud
Updated at December 12, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for output_to_lockbox
  • Import

Allows management of Yandex Cloud IAM OAuth client secret. The OAuth client secret is used for OAuth 2.0 client authentication.

Example usageExample usage

//
// Create a new OAuth Client Secret.
//
resource "yandex_iam_oauth_client_secret" "my-oauth-client-secret" {
  oauth_client_id = yandex_iam_oauth_client.my-oauth-client.id
  description     = "secret for oauth client"
  pgp_key         = "keybase:keybaseusername"
}

SchemaSchema

RequiredRequired

  • oauth_client_id (String) ID of the OAuth client to create a secret for.

OptionalOptional

  • description (String) The resource description.
  • output_to_lockbox (Block List, Max: 1) option to create a Lockbox secret version from sensitive outputs (see below for nested schema)
  • pgp_key (String) An optional PGP key to encrypt the resulting secret value. May either be a base64-encoded public key or a keybase username in the form keybase:keybaseusername.

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • encrypted_secret_value (String) The encrypted secret value, base64 encoded. This is only populated when pgp_key is supplied.
  • id (String) The ID of this resource.
  • key_fingerprint (String) The fingerprint of the PGP key used to encrypt the secret value. This is only populated when pgp_key is supplied.
  • masked_secret (String) The masked value of the OAuth client secret.
  • output_to_lockbox_version_id (String) ID of the Lockbox secret version that contains the value of secret_key. This is only populated when output_to_lockbox is supplied. This version will be destroyed when the IAM key is destroyed, or when output_to_lockbox is removed.
  • secret_value (String, Sensitive) The secret value. This is only populated when neither pgp_key nor output_to_lockbox are provided.

Nested Schema for Nested Schema for output_to_lockbox

Required:

  • entry_for_secret_value (String) entry that will store the value of secret_value
  • secret_id (String) ID of the Lockbox secret where to store the sensible values.

ImportImport

Warning

Import for this resource is not implemented yet.

Was the article helpful?

Previous
iam_oauth_client
Next
iam_service_account
© 2025 Direct Cursus Technology L.L.C.