How to extend Okta to any on-prem, legacy app | Strata.io

Name: How to extend Okta to any on-prem, legacy app | Strata.io
Ingredients: Extend Okta’s modern authentication and authorization to any legacy app; Deploy in hours without navigating change management or app downtime; Protect all apps — no matter where they are — without disrupting the user experience; What the user sees; What the admin does; 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 Okta.; Quick authentication. The user enters their login details, gets authenticated and logs in. Everything in the app looks the same as before.; 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 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.

www.strata.io

Deploy Okta and protect headers- and forms-based or LDAP-bound apps without refactoring. Add passwordless multi-factor authentication to any app — even if it do

View Original

Share this recipe:

Ingredients

Extend Okta’s modern authentication and authorization to any legacy app
Deploy in hours without navigating change management or app downtime
Protect all apps — no matter where they are — without disrupting the user experience
What the user sees
What the admin does
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 Okta.
Quick authentication. The user enters their login details, gets authenticated and logs in. Everything in the app looks the same as before.
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 <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.