Okta features travel through a regular lifecycle:
Note: Okta reserves the right to add new parameters, properties, or resources to the API without advance notice. These updates are non-breaking because they're additive. Follow the compatibility rules to ensure that your application doesn't break when additive changes are made. Breaking changes such as removing or renaming an attribute are released as a new version of the API, and Okta provides a migration path for new API versions.
Changes, regardless of lifecycle stage, are always reported in the Okta API Product Release Notes.
|Contact with Product team||✓||✗||✗||N/A|
|API changes||Subject to change||Backwards compatible||Backwards compatible||N/A|
|Announced in release notes||✗||✓||✓||✓|
|In Preview orgs||By invitation or self-service, depending on the feature||By request or self-service, depending on the feature||✓||✓|
|In Production orgs||✗||By request or self-service, depending on the feature||✓||✓|
The Product team manages and supports features in Beta. Beta features have been internally validated for a set of use cases. Minimal documentation is directly provided to customers for API-related Beta releases and is normally not publicly hosted. API endpoint and configuration information are usually supplied.
Important: Okta only enables Beta features in Preview org environments because features in Beta aren't supported by Okta Customer Support and may change at any time during the Beta release.
Okta selects a few customers for early testing of features in a Beta release. Customers participating in a Beta program agree to provide feedback that is required for maturing the feature. However, the timeline for addressing specific areas of feedback (including bugs) is determined by Okta market requirements for that feature.
Beta releases are managed in two ways:
- Beta: Involves regular contact with Okta, which may include conference calls between you and Okta that cover specific use cases, deployment guidance, and feedback. Betas are also announced to customers through the Ozone newsletter and communities. Okta may also solicit customers to participate in a Beta through email.
- Beta (Self-Service): Self-directed without ongoing support or regular contact with Okta. Contact is primarily limited to collecting feedback. If you're interested in a Beta Self-Service feature, you can enable that feature for your org from the Settings > Features page in the Admin Console.
You can track the availability of Beta features on the Product Roadmap page.
See Manage Early Access and Beta features for more information on Okta's Self-Service Feature Manager.
A feature in an Early Access (EA) stage is new or enhanced functionality made available for you to selectively opt in to and use in both Production and non-Production environments.
Note: A feature may skip EA if it doesn't affect other features or functionality. Also, although Okta strives for API-first development, a feature in EA may add functionality later.
Any bug fixes or improvements are managed and fixed with the same timeline and processes as those in General Availability.
Features in an EA release are marked with the EA icon:
EA releases are managed in two ways:
- Early Access: If you're interested in an EA feature, you must contact Support to enable the feature. Support can enable features in EA for any customer, provided any required prerequisites have been met.
- Early Access (Self-Service): If you're interested in an EA Self-Service feature, you can enable the feature for your org from the Settings > Features page in the Admin Console.
You can track the availability of EA features on the Product Roadmap page.
See Manage Early Access and Beta features for more information on Okta Self-Service Feature Manager.
A feature in General Availability (GA) is new or enhanced functionality that is enabled by default for all customers. Beginning in February 2017, features move from EA (enabled by request) to GA (enabled for all orgs) in a regular cadence:
- EA features become GA in Preview orgs in the first release of the month.
- These same features become GA in Production orgs in the first release of the next month.
Features in GA are supported by Okta Customer Support and issues are addressed according to your Customer Agreement with Okta.
Documentation for features in GA release isn't marked with any icons.
A feature identified as deprecated is no longer recommended for use and may be removed in the future. Generally, this means that you shouldn't use it unless you have to. Any workarounds or recommended paths forward are included in the relevant documentation, libraries, or references. When Okta schedules an end-of-service plan, that information is also included.
Documentation for features that have been deprecated are marked with the Deprecated icon.
Some changes may not go through the full Beta-EA-GA lifecycle:
- Bug fixes that change only the incorrect behavior of the bug.
- Cosmetic changes, such as changing the label of a field in the Admin Console.
- Changes that are narrow in scope or effect, or purely additive, such as adding a new attribute.
Changes like these may be released to Preview orgs any week of the month and appear in production the next week.
Other exceptions include:
- Occasionally, a feature is released using an iterative, custom schedule to enable close monitoring. Such features may spend more than one month between preview and production for their GA release.
- Features exposed in the Admin Console may be EA or GA without the corresponding API being in the same stage of the lifecycle, or available at all.
As with all changes that affect our customers, changes outside of the regular Beta-EA-GA lifecycle are reported in the Okta API Release Notes.