← Back to Recipes

How to extend your modern IDP to any home-grown app

Don’t lose mission-critical apps because modernizing them feels impossible — protect every home-grown app with your favorite modern identity service instead.

Read the docsTry this in Maverics
  • Keep the apps the business relies on and maintain the complex access policies you love.
  • Extend modern identity and SSO to home-grown apps in minutes, without ever touching the code.
  • Bring every app in line with cyber insurance qualifications and close your security gaps.
Ingredients
Modern Authentication Non-standard App Modern IDP

Don’t abandon your impossible apps. Modernize them.

Recipe details

This is how everything works together.

Setup details

Just add in your ingredients and deploy.

What the admin does

Don’t leave mission-critical apps unprotected. Use Identity Orchestration to extend any modern identity provider to every app — even if you can’t access (or understand) the source code.

  • 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 your new modern 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.

What the user sees

Switching to a modern IDP stopped being optional when support started crumbling. Use Identity Orchestration to modernize and leave your legacy fast.

  • 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 your new modern 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.

Solve more modernization challenges with ready-to-deploy recipes

Identity Continuity
Active Directory (AD)
Okta
Failover from Okta to on-prem Active Directory (AD)

Keep your critical apps accessible. Use Identity Continuity to allow key users to securely authenticate locally with Keycloak if Microsoft Entra ID ever becomes unavailable.
Identity Continuity
Okta
Entra ID (Azure AD)
Failover from Okta to Microsoft Entra ID

Don’t let Okta take you offline. Use Identity Continuity to allow users to securely authenticate to critical apps with Microsoft Entra ID anytime Okta is unavailable.
Identity Continuity
Keycloak
Entra ID (Azure AD)
Failover from Microsoft Entra ID to on-prem Keycloak

Keep your critical apps accessible. Use Identity Continuity to allow key users to securely authenticate locally with Keycloak if Microsoft Entra ID ever becomes unavailable.

View all recipes

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