On This Page
Okta publishes a number of officially-supported libraries and SDKs on GitHub. These libraries follow a consistent versioning and release pattern, described here. Note that this is separate from how Okta's HTTP APIs are versioned and released.
You can see a list of all our library versions and their support status at the bottom of this page.
All of our libraries and SDKs follow semantic versioning. Library versions will always be
major.minor.patch - for example,
- Increase the patch version for bug fixes, security fixes, and code documentation. Backwards compatible; no breaking changes.
- Increase the minor version for new features and additions to the library's interface. Backwards compatible; no breaking changes.
- Increase the major version for breaking changes to the library's interface or breaking changes to behavior.
Semantic versioning means that within a major version, you can safely apply minor and patch updates without your code breaking. The status of each major version series (for example,
2.x) follows this lifecycle:
Beta versions are currently in development and are not ready for production use. While a library version is in beta, the code interface is not final and breaking changes could occur without warning.
New libraries (or new major versions of existing libraries) typically stay in beta for a period of time while we iterate on the design and get feedback from the community. When the library is ready for production, it will be marked as stable.
Stable version series are supported by Okta for use in production code. Semantic versioning means that a stable major version may get new features (minor updates) or bug fixes (patch updates), but no breaking changes.
When a new major version of a library is released, the old major version series will be marked as retiring. Retiring libraries are supported by Okta for at least nine months. After this period of time, the version series will be officially retired (below).
For example, if version 2.0.0 of
okta-sdk-foobar is published in January, the 1.x series of
okta-sdk-foobar (any version starting 1) will be officially supported until at least September. The retirement dates will be posted in the library's readme or documentation.
Retired version series are no longer supported by Okta, and are no longer recommended for production use. Okta will not publish new features or bug fixes for retired versions, except for critical security fixes (at our discretion).
For example, after
okta-sdk-foobar version 1.x has a retiring period (of at least nine months), it is no longer supported. Customers and developers are encouraged to upgrade to 2.0.0 or later.
When in doubt, check GitHub! The library's readme will clearly state any versions that are retiring or have been retired.
This table lists the current (and historical) major versions of our open-source libraries and tools. The most up-to-date information is always available from the GitHub readme of a particular project.
|Sign-In Widget||1.13.0 |
|Retiring on 2019-05-31|
|Android AppAuth SDK||0.2.4||Retiring on 2020-03-20|
|Angular SDK||0.1.0 |
|ASP.NET Core SDK||1.x||Stable|
|JWT verifier for Go||0.x||Beta|
|OIDC iOS (formerly iOS AppAuth SDK)||1.x |
|Retiring on 2019-07-19|
Retiring on 2020-01-16
|iOS OktaJWT||0.1.0 |
|iOS authentication SDK||0.1.0||Beta|
|Java management SDK||0.0.x |
|Java authentication SDK||1.x||Stable|
|JWT verifier for Java||0.x||Stable|
|Spring Boot Starter||0.x||Stable|
|.NET management SDK||0.3.3 |
|Retiring on 2019-12-11|
|.NET authentication SDK||1.x||Stable|
|Node.js management SDK||1.2.0 |
|Retiring on 2020-01-03|
|JWT verifier for Node.js||0.x||Stable|
|OpenID Connect middleware for Node.js||0.1.2||Beta|
|PHP management SDK||0.2.0 |
|PowerShell Module||1.0.2||Retiring on 2020-04-26|
|JWT verifier for PHP||0.x||Stable|
|React SDK||0.0.13 |
|React Native SDK||0.1.0 |
|Retiring on 2020-04-08|
|Vue SDK||0.1.0 |