How to modernize off PingFed and PingAccess to Azure AD | Strata.io

Name: How to modernize off PingFed and PingAccess to Azure AD | Strata.io
Ingredients: Lower your modernization budget and your team’s stress levels. Move any app to Azure in days instead of months — without refactoring.; Reduce architectural complexity. Embrace agility and put the tools you already have to work.; Future proof your stack. Cut down your on-prem footprint with Identity Orchestration — zero active upkeep needed.; 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 the new IDP.; Quick authentication. The user enters their IDP details, gets authenticated and logs in. Everything in the app looks the same as before.; Prepare your work surface. Set the application HTTP-POST config in the orchestrator and set the application to point to the orchestrator as the LDAP server.; Set the rules. Define the basic policy that enforces authentication to your app and define how Maverics will provide context to the upstream application.; Configure. Using the declarative YAML-based config file, set Maverics up as an authentication gateway and give it the right permissions to direct users correctly.

www.strata.io

Follow our Identity Orchestration recipe to learn how to shrink your Ping instance and move to Azure AD without costly professional services.

View Original

Share this recipe:

Ingredients

Lower your modernization budget and your team’s stress levels. Move any app to Azure in days instead of months — without refactoring.
Reduce architectural complexity. Embrace agility and put the tools you already have to work.
Future proof your stack. Cut down your on-prem footprint with Identity Orchestration — zero active upkeep needed.
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 the new IDP.
Quick authentication. The user enters their IDP details, gets authenticated and logs in. Everything in the app looks the same as before.
Prepare your work surface. Set the application HTTP-POST config in the orchestrator and set the application to point to the orchestrator as the LDAP server.
Set the rules. Define the basic policy that enforces authentication to your app and define how Maverics will provide context to the upstream application.
Configure. Using the declarative YAML-based config file, set Maverics up as an authentication gateway and give it the right permissions to direct users correctly.