Old application not working with MFA enabled

I’m sure I know the answer to this question, but I thought I would ask here anyway. My team inherited a .net app that uses ComponentSpace and does saml impersonation with Okta. We have started testing MFA and notice that the app no longer works for any users in our test MFA group. I assume since MFA requires extra authentication via a code, there is no way to mimic that in the application. Is there a workaround?

The MFA should be handled entirely within Okta. Exactly how the user is authenticated at the identity provider (ie Okta) shouldn’t impact the service provider (ie your ASP.NET application).

Please provide more details regarding the issue.

After completing MFA, does control return to your application?

If so, what happens next? Is an exception being thrown? What’s the stack trace?