-
Okta Provider Terraform, Data Source: okta_app_oauth Get a OIDC application from Okta. all the restrictions associated with the 'Catch All' rule. Showing 1 - 4 of 8 available modules Get started Terraform uses plugins called Providers to communicate with a managed service. Each managed resource in the Okta provider (e. Start with the Terraform overview, and then see Enable Terraform access to set up Terraform with your Okta org. It describes the specific Makefile targets, the licensing constraints involved, and the data flow from the upstream Okta Terraform provider into the provider-okta 3 days ago · The Okta provider utilizes the Upjet framework to bridge Kubernetes managed resources with the Okta Terraform provider. To automate your Okta org, you use the Okta Terraform Provider. Example Usage Schema Optional active_only (Boolean) Search only ACTIVE applications. . This architecture enables the provider to leverage the mature resource logic of the okta/okta Terraform provider while exposing a native Kubernetes API through Custom Resource Definitions (CRDs). label (String) The label of the app to retrieve, conflicts with label_prefix and id. 3 days ago · This page details the automated process for acquiring the Terraform provider schema and documentation, which serves as the foundation for the Crossplane provider generation. Therefore the Okta Terraform Provider does not support this resource for Classic orgs. The provider contains many components that provide the functionality to manage parts of your org, such as groups and applications. This automation ensures that the provider remains synchronized with the underlying okta/okta Terraform provider. These settings are consumed by the controller to initialize the Okta Terraform provider, which performs the actual API calls. This page details how the provider initializes the Terraform workspace, extracts credentials from Kubernetes ProviderConfig secrets, and configures the underlying Terraform engine to communicate with the Okta API. A Terraform provider to manage Okta resources, enabling infrastructure-as-code provisioning and management of users, groups, applications, and other Okta objects. 3 days ago · The provider-okta is built using the Upjet framework, which automates the creation of Crossplane providers by wrapping existing Terraform providers. The Okta Provider is the plugin that enables you to manage your Okta org with Terraform. Modules are self-contained packages of Terraform configurations that are managed as a group. These files define the logic required to bridge Kubernetes resource lifecycle events with Terraform operations. - Releases · okta/terraform-provider-okta Feb 23, 2026 · A practical guide to configuring the Okta provider in Terraform for managing applications, users, groups, policies, and SSO configurations as code. Inside the product a sign-on policy is referenced as an authentication policy, in the public API the policy is of type 'ACCESS_POLICY'. Aug 12, 2022 · okta_app_signon_policy creates a default 'Catch All' rule. This resource allows you to create and configure a sign-on policy for the application. g. id (String) Id of application to retrieve, conflicts with label and label_prefix. Use the navigation to the left to read about the available resources and data sources. 3 days ago · The provider-okta codebase utilizes a standardized, code-generated pattern for its resource controllers. In case the provider configuration is still using old "oktadeveloper/okta" source, please change it to "okta/okta" and run terraform The Terraform Okta provider is a plugin for Terraform that allows for the full lifecycle management of Okta resources. , GroupAssignment, OAuthApp, SAMLApp) has a corresponding zz_controller. Once such a rule is created, it's difficult to change anything about it with terraform since the codebase implementing okta_app_signon_policy_rule is designed to work with mutable rules vs. Contact support for further information. 3 days ago · The Okta provider uses a standard Crossplane ProviderConfig to define global settings and credential sources. 3 days ago · The provider-okta project utilizes a sophisticated build system based on GNU Make and the build/makelib submodule. 3 days ago · The provider-okta codebase leverages the Upjet framework to automate the creation of Kubernetes Custom Resource Definitions (CRDs), Go type definitions, and controller logic. Jun 10, 2026 · When migrating from okta_app_signon_policy_rule (single-rule resource) to okta_app_signon_policy_rules (grouped resource): Old behavior: Single-rule resource defaults to priority = 0 in Terraform state, even if Okta assigned a different priority. This provider is maintained internally by the Okta development team. This system automates the lifecycle of the provider, from extracting schemas from the upstream Okta Terraform provider to generating Go code, building container images, and executing end-to-end tests. Okta Provider The Okta provider is used to interact with the resources supported by Okta. go file generated by Upjet. The provider needs to be configured with the proper credentials before it can be used. fkw8, nsuzeg, hvdb, cwjt, cpxpet, 4ary6, jsewg, eermz, hqdz, v0a6h,