← Back to Recipes

How to move from SiteMinder to Microsoft Entra ID (Azure AD)

SiteMinder’s end of service is coming. Use this recipe to replace SiteMinder with Microsoft Entra ID (Azure AD) without refactoring your apps.

Read the docsTry this in Maverics
  • Quickly move an application from a legacy IDP, like SiteMinder, to a modern cloud IDP provider, like Microsoft Entra ID (Azure AD) – all without the need to refactor any apps
  • Future-proof applications via an identity abstraction layer to quickly add new app modernization and identity authentication services such as MFA, passwordless, or identity verification at any time
  • Leverage automation to replicate the identity authentication and authorization process at scale for all your applications and migrate from SiteMinder, or any other end-of-life legacy IDP vendors
Ingredients
Migration CA SiteMinder Entra ID (Azure AD)

Leave a real legacy by modernizing identity authentication architecture before the clock runs out on SiteMinder

The recipe diagram

A simple Identity Orchestration user journey that simply works.

The sequence diagram

How everything comes together to provide identity authentication.

What the user sees

App users don’t care what IDP you authenticate with — they care that it works. Use Identity Orchestration to deliver consistent management across all your apps.

  • Familiar login. Users head to the same screen and start the app identity authentication flow.
  • Invisible redirection. Behind the scenes, Maverics evaluates the app policy in config and directs the user to Microsoft Entra ID (Azure AD).
  • Quick authentication. The user enters their Microsoft Entra ID (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 and migrate off of SiteMinder 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 identity authentication to Microsoft Entra ID (Azure AD) 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

Leave SiteMinder for a modern IDP

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