Loading post…
OktaE. DunhamAnnouncement
Changes Are Coming to the Okta Developer Edition Organizations
Summary
Okta is replacing Developer Edition organizations with the Integrator Free Plan as the default developer organization type on May 22, 2025, as part of architectural changes tied to its Secure Identity Commitment. The new organization is intended for iterative integration development, identity-flow validation, and OIN preparation, not production use, and provides access to expanded testing offerings and support resources. Existing Developer Edition organizations begin deactivation on July 18, 2025, in batches, after which users lose access to their organizations and resources. Migration choices include recreating resources with automation, generating Terraform configurations with Terraformer, or using EnvSync to back up supported objects and recreate many of them. Published OIN integrations remain available, but linking them to the new account requires contacting Okta; draft or in-review submissions from Developer Edition must be approved by June 9 or will be automatically declined and require resubmission.
Context
Okta is changing its developer organization model and deprecating existing Developer Edition organizations. The new Integrator Free Plan supports pre-production integration work, identity-flow testing, and OIN preparation, but neither organization type is intended for production use.
Approach / What changed
Users should create an Integrator Free Plan organization and migrate needed work. Options include rerunning setup automation, using Terraformer to generate Terraform configurations, using EnvSync for a one-off backup and recreation of supported objects, or manually recreating resources. Published OIN integrations can be linked to the new account by contacting Okta, while unaccepted work must be migrated by its owner.
Takeaways
New Developer Edition organizations stop being created on May 22, 2025; the developer.okta.com signup flow creates an Integrator Free Plan organization instead.
Developer Edition organizations begin deactivation on July 18, 2025, in batches, and their users will lose access to the organizations and all resources in them.
Draft or In Review OIN submissions from Developer Edition organizations must be approved by June 9, 2025, or they will be automatically declined and require resubmission from an Integrator Free Plan organization.
FAQ
What happens to a published OIN integration when a Developer Edition organization is deactivated?
A published integration remains available to users without interruption because Okta keeps its own copy for distribution. To update it from an Integrator account, contact [email protected] with the account ID and a link to the OIN catalog entry.
Which migration tools can recreate an existing Developer Edition setup?
Existing automation can be rerun after supplying credentials for the Integrator organization. Terraformer can generate Terraform configurations from existing resources, while EnvSync can create backup files for supported objects and automatically recreate many of them.
What happens to an OIN integration that is still in progress?
Work on an integration that has not been accepted must be migrated by its owner. Draft or In Review submissions from Developer Edition must be approved by June 9, 2025, or they are automatically declined and must be resubmitted from an Integrator Free Plan organization.
Source and freshness
- Source
- developer.okta.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.