<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
0D54z0000AIb8SkCQJOkta Classic EngineAuthenticationAnswered2024-12-31T16:49:27.000Z2024-12-05T17:20:19.000Z2024-12-31T16:49:27.000Z
Okta 400 bad request error on sign-out with no details to help troubleshoot.

I am trying out Okta login / logout in okta-aspnetcore-mvc-example sample code and everything runs fine. However, in my test app, I keep receiving the following error on the logout. What is the best way to troubleshoot this? I did search the help center but could not find anything helpful. Any tip/suggestion would be appreciated.

 

Thank,

 

/help/servlet/rtaImage?refid=0EM4z000007IoUv


  • Paul S. (Okta, Inc.)

    Hello @00urncm0fGsdNobYk356m1.56139295220643E12 (Customer)​ Thank you for posting on our Community page!

     

    The error points towards an authentication policy which may or may not be misconfigured.

    In alignment with the Okta Secure Identity Commitment, Okta is requiring customers to use multifactor authentication (MFA) to access their Okta Admin Console. MFA is an effective tool to protect against identity attacks.

    We are in the process of rolling this out and you should expect that this will be completed in Q4.

    The MFA will be required on all orgs and no admins will be exempt.

    We recommend reviewing the Frequently Asked Questions article on this subject.

     

    If you have a production account with us, please leverage it to open a case via the support.okta.com site or call the support line so our colleagues can investigate and confirm if the issue is related.

    If for whatever reason those options are not available for you, please contact your Okta Account Executive or Customer Success Manager, and they will be able to engage the Support team on your behalf. 

     

    If no paid developer or production account is available, the only option left is to sign up for a new free trial or developer account.

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Ask Us Anything about Okta FastPass - now thru December 11th.

    Expand Post
    Selected as Best
  • Paul S. (Okta, Inc.)

    Hello @00urncm0fGsdNobYk356m1.56139295220643E12 (Customer)​ Thank you for posting on our Community page!

     

    The error points towards an authentication policy which may or may not be misconfigured.

    In alignment with the Okta Secure Identity Commitment, Okta is requiring customers to use multifactor authentication (MFA) to access their Okta Admin Console. MFA is an effective tool to protect against identity attacks.

    We are in the process of rolling this out and you should expect that this will be completed in Q4.

    The MFA will be required on all orgs and no admins will be exempt.

    We recommend reviewing the Frequently Asked Questions article on this subject.

     

    If you have a production account with us, please leverage it to open a case via the support.okta.com site or call the support line so our colleagues can investigate and confirm if the issue is related.

    If for whatever reason those options are not available for you, please contact your Okta Account Executive or Customer Success Manager, and they will be able to engage the Support team on your behalf. 

     

    If no paid developer or production account is available, the only option left is to sign up for a new free trial or developer account.

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Ask Us Anything about Okta FastPass - now thru December 11th.

    Expand Post
    Selected as Best
This question is closed.
Loading
Okta 400 bad request error on sign-out with no details to help troubleshoot.