← Back to Recipes

How to add Trusona to any non-standard legacy app

Protect every vulnerable, mission-critical app with passkey authentication.

Read the docsTry this in Maverics
  • Add modern passwordless protection to any legacy app without refactoring
  • Enable fine-grained authorization policies at page and resource level
  • Delight users with a quick, simple and secure sign-in experience
Ingredients
MFA Non-standard App Trusona

App-free instant authentication. Zero code. Zero friction.

Recipe details

See how simple it really is.

Setup details

Just add your ingredients and deploy.

What the user sees

App users don’t really care what passwordless provider or login authenticator you use — they care about a smooth, login experience that doesn’t involve excessive app jumping. Use Identity Orchestration to deliver that.

  • 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 Trusona.
  • Quick, smooth passkey authentication. The user uses their phone’s existing biometric and passkey support to access the target app in seconds. Everything in the app looks the same as before.

What the admin does

Using a modern passwordless provider isn’t a ‘nice-to-have’ anymore — it’s a security essential. Identity Orchestration makes adding passwordless from Trusona easy.

  • 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 Trusona 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 modernize any app in 10 mins?

Let us prove to you how easy this can be and demo a complete app modernization experience in under 10 min.

Book a demo