← Back to Recipes

How to move from your legacy IDP to CyberArk Identity without refactoring a thing

Break up with your outdated IDP, keep the complex access policies you love, and replace it with modern authentication and passwordless protection from CyberArk Identity — all without rewriting your apps.

Read the docsTry this in Maverics
  • Give every app the full protection of CyberArk — even legacy ones that don’t ‘speak’ modern identity protocols or are located on-prem
  • Keep your existing access policies and take a low-risk, phased coexistence approach to migration off your existing IDP
  • Fully retire your legacy identity license and support costs, and easily adopt the latest CyberArk security services such as passkeys without disrupting users
Ingredients
Migration CyberArk Non-standard App

Modernize any app for good. Ensure secure access for all.

Recipe details

This is how everything works together.

Setup details

Just add in your ingredients and deploy.

What the user sees

App users don’t care what identity provider you use to authenticate them — they care that it works. Use Identity Orchestration to make sure it works perfectly every time.

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

What the admin does

Switching to a modern IDP like CyberArk Identity stopped being optional when support for your existing one 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 for CyberArk 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.

See it in action

Protect non-standard apps with CyberArk Identity

Interested to see more? We have a full workshop for you!

Watch now

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