← Back to Recipes

How to move from OAM to Azure AD

Oracle Access Manager is challenging to maintain and provides limited app protection possibilities. Use this recipe to replace it with Azure AD without refactoring your apps.

Read the docsTry this in Maverics
  • Quickly modernize authentication of an application from a legacy IdP to a modern cloud one like Azure AD without the need to refactor the app
  • Future-proof the application via identity abstraction to quickly add new post-modernization identity services such as MFA, Passwordless, or Identity Verification
  • Leverage automation to replicate the process at scale for all your applications and retire your EOL legacy vendor contracts
Ingredients
Migration OAM Entra ID (Azure AD)

Leave a real legacy by modernizing authentication architecture

The recipe diagram

A simple user journey that simply works.

The sequence diagram

How everything comes together to authenticate.

What the user sees

App users don’t care what IDP you authenticate with — they care that it works. Use Identity Orchestration to deliver smooth consistency.

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

What the admin does

Switching to a modern IDP 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 AzureAD and define how Maverics will provide context to the upstream application.
  • Configure. Using the declarative YAML-based config file, set Maverics up as an authentication gateway and give it the right permissions to direct users correctly. 

See it in action

Protect on-prem apps with Microsoft Entra ID

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