- Make the most of Duo SSO and protect any legacy app without coding
- Launch in minutes with zero app changes and no downtime
- Secure all apps with strong authentication without disrupting the user experience
App users don’t care what MFA or authentication tool you use to make sure they are who they say they are — 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 with their usual log-in details.
- Invisible redirection. Behind the scenes, Maverics evaluates the app policy in config and, after the user logs in, directs the user to Duo SSO.
- Quick, simple authentication. The user gets authenticated by the modern IDP or AD as usual. After login, Duo SSO triggers an additional authentication based on the user’s preferences. Everything in the app looks the same as before.
Using passwordless MFA to secure identity is essential for multi-cloud enterprises. Identity Orchestration makes adding Duo SSO everywhere easy — even if you’re dealing with legacy apps.
- 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 Duo SSO 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
Quickly protect any resource with Passwordless MFA (PMFA) and register new users without disruption to the access workflow.
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.
Oracle Access Manager is challenging to maintain and provides limited app protection possibilities. Use this recipe to replace it with Okta without refactoring your apps.
SiteMinder’s end of service is coming. Use this recipe to replace it with Azure AD without refactoring.