Stormpath is Joining Okta

We are incredibly excited to announce that Stormpath is joining forces with Okta. Please visit the Migration FAQs for a detailed look at what this means for Stormpath users.

We're available to answer all questions at [email protected].

What does this mean for developers who are using this library?

• If you have upgraded to the 2.x series from 1.x, you should downgrade to 1.1.1. Why? The 2.x series depends on the Stormpath Client API, which will not be migrated to the Okta platform.
• When downgrading to 1.1.1 you will need to use one of our backend framework integrations to serve the APIs that the 1.x series depends on.
• These backend integrations are being patched to work with Okta:

• Java Spring
• Java Spring Boot
• Node Express
• ASP.NET 4.x
• ASP.NET Core

• If you are using the Express integration, please see the Express-Stormpath Angular Sample Project, it can be used to test your migration to Okta.

README

If you are actively using this library, you can find the old readme in OLD-README.md. It is not possible to register for new Stormpath tenants at this time, so you must already have a Stormpath tenant if you wish to use this library during the migration period.