<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
0D5KZ00001K7qYz0AJOkta Classic EngineAuthenticationAnswered2025-09-05T20:46:15.000Z2025-09-01T15:08:02.000Z2025-09-05T20:46:15.000Z
  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hello @RabiulA.72028 (Customer)​ , thank you for contacting Okta Community!

     

    I've reviewed our documentation for something relevant. It looks like your question is more appropriate for our dedicated Okta Developer Forum. I advise reaching out via devforum.okta.com  as they will have more insight into this topic. 

    In the meantime, you can reference this articles: 

    Error "400 Bad Request" when Redirecting to the /authorize Endpoint with no Error Description

     

    While we'll do our best to answer your questions here, this medium is more inclined towards Okta's core products and features (non-developer work).

     

    Regards. 

    --

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

    Just released: More Okta Community badges just added

    Expand Post
  • KathyT.73511 (Anthropic Identity)

    The error code refers to the Policy. Under Security - API, click on the Authorization server you are using and then go to the Access Policy. Make sure you have the right Grant Type and the correct scopes. Also, because you said it worked before, check your token options.

     

    If you don't have a policy for your app, I would suggest that you create one. It may make it easier to troubleshoot.

    Expand Post
  • BrandonB.06003 (Customer)

    check the authorization server policy to see if there are any restrictions. and also check the okta system log to see if there is more detailed information on the error

This question is closed.
Loading
Okta single page authentication not working suddenly