Failover from Okta to on-prem Active Directory (AD) | Strata.io

Name: Failover from Okta to on-prem Active Directory (AD) | Strata.io
Ingredients: Protect against natural disasters, broken configurations, or network loss. Automatically failover to on-prem AD so users can access apps until the issue is fixed.; Make attributes and policies consistent between Okta and AD. Seamlessly map common attributes with the Schema Abstraction Layer™. .; What the user sees; What the admin does; Familiar login. Users log in via the Microsoft Entra ID portal and follow the authentication access flow.; Invisible redirection. Behind the scenes, Maverics makes sure that your Microsoft Entra ID instance is online and — if there are any challenges — directs the user to Active Directory.; Quick authentication. The user enters their details, gets authenticated and logs in. Everything in the app looks the same as before and access is granted.; Define your strategy. Set Okta as your primary IDP and configure AD as your secondary IDP to define your failover strategy within the Maverics UI.; Define the attributes your application needs in the Schema Abstraction Layer™. Separately map them to claims available from Okta and Active Directory.

www.strata.io

Use Identity Continuity to allow key users to securely authenticate with AD if Okta goes down.

View Original

Share this recipe:

Ingredients

Protect against natural disasters, broken configurations, or network loss. Automatically failover to on-prem AD so users can access apps until the issue is fixed.
Make attributes and policies consistent between Okta and AD. Seamlessly map common attributes with the Schema Abstraction Layer™. .
What the user sees
What the admin does
Familiar login. Users log in via the Microsoft Entra ID portal and follow the authentication access flow.
Invisible redirection. Behind the scenes, Maverics makes sure that your Microsoft Entra ID instance is online and — if there are any challenges — directs the user to Active Directory.
Quick authentication. The user enters their details, gets authenticated and logs in. Everything in the app looks the same as before and access is granted.
Define your strategy. Set Okta as your primary IDP and configure AD as your secondary IDP to define your failover strategy within the Maverics UI.
Define the attributes your application needs in the Schema Abstraction Layer™. Separately map them to claims available from Okta and Active Directory.