How to extend Okta to any on-prem, legacy app

Deploy Okta and protect headers- and forms-based or LDAP-bound apps without refactoring.

Read the docsTry this in Maverics
  • Extend Okta’s modern authentication and authorization to any legacy app
  • Deploy in hours without navigating change management or app downtime
  • Protect all apps — no matter where they are — without disrupting the user experience

MFA everywhere starts with Okta everywhere

Recipe details

See how simple it really is.

Sequence details

This is how everything works together.

Setup details

Just add your ingredients and deploy.

App users don’t care what IDP you authenticate with — they care that it works. Use Identity Orchestration to deliver smooth consistency so that users get the Okta SSO experience for every app.

  • Familiar login. Users head to the same screen and start the app authentication flow.
  • Invisible redirection. Behind the scenes, Maverics evaluates the app policy in config and directs the user to Okta.
  • Quick authentication. The user enters their login details, gets authenticated and logs in. Everything in the app looks the same as before.

Switching to Okta stopped being optional when support started crumbling. Use Identity Orchestration to modernize for good.

  • Prepare your work surface. Define the upstream application and the port Maverics will use to communicate with the app.
  • Set the rules. Define the basic policy that enforces authentication to <IDP> and define how Maverics will provide context to the upstream application.
  • Configure. Set Maverics up as an authentication gateway and give it the right permissions to direct users correctly.

Ready to cook up your perfect identity modernization solution?

Stop juggling disparate identity services. Unleash the power of Strata’s orchestration recipes.
Whether you’re dealing with legacy app modernization or controlling multi-cloud access, Orchestration Recipes have got you covered.

Read the docsTry this in Maverics