← Back to Recipes

How to protect every app if PingOne goes down

Don’t get hurt by unexpected outages. Use Identity Orchestration to keep mission-critical apps working while repairs are underway.

Read the docsTry this in Maverics
  • Turn any IDP into an emergency back-up and extend it to key business apps.
  • Automatically pivot apps to LDAP, active directory, different PingOne instance, or another cloud IDP during an outage.
  • Seamlessly switch back to PingOne once order has been restored.
Ingredients
Identity Continuity Modern IDP PingOne

Keep your apps ready for anything

What the admin does

A lightweight back-up can keep mission-critical apps online during an unexpected outage so that the business doesn’t suffer. Use Identity Orchestration to extend one of your cloud IDPs or on-prem solution to any critical app so that they can failover smoothly in times of need.

  • 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 the failover 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

App users don’t care about IDPs or outages — they care that their apps are always accessible. Use Identity Orchestration to make it so.

  • 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 <IDP Name>.
  • Quick authentication. The user enters their <IDP Name> details, gets authenticated and logs in. Everything in the app looks the same as before.

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