← Back to Recipes

How to simplify app access when you’re dealing with multiple IDPs

Let any user log into a shared app with their group IDP — without disrupting the login experience or losing control over who sees what.

Read the docsTry this in Maverics
  • Give any type of user immediate access to the shared resources they need without creating new user accounts
  • Support multiple identity providers (cloud-based or legacy!) for any app
  • Set IDP and resource-level custom access policies in seconds so everyone sees exactly what they’re supposed to
Ingredients
Identity Continuity Modern Authentication Multiple IDPs

See it in action

Manage app access when using multiple IDPs

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

Watch now

What the user sees

App users don’t care what identity provider you use to authenticate them — they just want to keep using their current login details. Use Identity Orchestration to keep log-in simple and secure, and make sure users see exactly what they’re supposed to.

  • Familiar login. Users head to the same screen and start the app authentication flow.
  • Invisible redirection. Behind the scenes, Maverics evaluates the username context in config and directs the user to the correct IDP.
  • Quick authentication. The user follows their usual IDP workflow, gets authenticated and logs in. Everything in the app looks the same as before.

What the admin does

Using different IDPs to authenticate users can make perfect sense— as long as you have 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.

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

See it in action

Keep mission critical apps on with Identity Continuity

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

Watch now