← Back to Recipes

Secure & control cross-border access to a global resource

Keep your employee data sovereign, local and resident. Support your multi-national operations with region-specific IDPs that give users controlled access to common apps.

Read the docsTry this in Maverics
  • Store employee data within their hiring region to ensure corporate and regulatory compliance.
  • Apply your complex and distinct region or IDP-based access policies to any shared resource.
  • Enforce country-level controls no matter where users actually log-in from.
Ingredients
Modern Authentication Multiple IDPs

Control region-specific access in your global app architecture

Recipe details

This is how everything works together.

Setup details

Just add in your ingredients and deploy.

What the user sees

Your employees don’t care what identity provider you use to authenticate them — they care that it works. So use Identity Orchestration to give users the log-in experience they expect for the global resources they need while controlling region-specific access in the background. Even as they travel across regions.

  • Familiar login. Users head to the same screen and start the app authentication flow, regardless of where they are physically located.
  • Invisible redirection. Behind the scenes, Maverics evaluates the app policy in config and directs the user to their home region’s IDP.
  • Quick authentication. The user enters their log-in details, gets authenticated and logs in. Everything in the app looks the same as before.

What the admin does

Using different region-specific IDPs to authenticate users to common apps can make perfect sense— as long as you have strict control over access policies. Identity Orchestration gives you that.

  • 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 each 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.

See it in action

Control Cross-Border Access in Your Global Architecture

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