<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
0D51Y00007CBMF5SAPOkta Classic EngineAdministrationAnswered2024-04-16T09:19:02.000Z2019-12-03T15:16:56.000Z2020-01-08T16:08:00.000Z

6u2j9 (6u2j9) asked a question.

400 bad request error after redirecting to okta

The application team is trying to login to the application and it redirects to the okta stating error 400 bad request.

 

Checked the redirect uri and issuer, both are same in okta and application.

Image is not available


  • 6u2j9 (6u2j9)

    Hi Brian,

     

    Thanks for your reply. We have already created a case with the okta technical support team and it has been resolved. There was a misconfiguration from application team on the client id consists of a space which was identified by the your team and is resolved.

    Expand Post
    Selected as Best
  • Hi Arif,

     

    I suggest creating a case with our technical support team. They'll be happy to take a look at your configuration and help troubleshoot the issue.

     

    Thanks,

     

    Brian Anderson

    KCS Specialist

    Okta

    Expand Post
  • 6u2j9 (6u2j9)

    Hi Brian,

     

    Thanks for your reply. We have already created a case with the okta technical support team and it has been resolved. There was a misconfiguration from application team on the client id consists of a space which was identified by the your team and is resolved.

    Expand Post
    Selected as Best
This question is closed.
Loading
400 bad request error after redirecting to okta