<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009eatvrCAAOkta Classic EngineAuthenticationAnswered2026-03-23T04:16:57.000Z2023-09-11T11:59:56.000Z2023-09-13T06:48:49.000Z
Handling MFA for external IDPs

Hi,

I have setup an OIDC app. The app has default OKTA uses with username + password, & it also has a sign on policy for an Azure AD IDP.

Both sets of users are associated to an MFA policy (email or SMS).

I have 2 questions:

1) Is there a way to have the external users submit their MFA via a "Self-Hosted" okta widget, or via API's? At the moment, users are challenged for the MFA whilst on the okta hosted widget at ...okta.com/.../callback.

 

2) When on the okta.com/../callback page, the "back to signin" button just loops back on itself . Is there a way to fix this?

 

At the moment the flow is:

  • User goes to a page /signon-azure (server code redirects user with idp parameter)
  • Browser redirects to Okta.com.../authorize/..
  • Browser redirects to okta.com/sso/idps/...
  • Browser redirects to microsoft.com
  • Browser redirects back to okta.com/../callback
  • Whilst browser is at okta.com/callback, user can new trigger the sms/email
  • On success, user redirects back to local app/authorization-code/callback

 

Thanks,


This question is closed.
Loading
Handling MFA for external IDPs