<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
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D5KZ000010Ugqn0ACOkta Classic EngineIntegrationsAnswered2025-07-31T15:04:01.000Z2025-07-07T11:20:11.000Z2025-07-31T15:04:01.000Z

SergioM.66052 (Customer) asked a question.

July 7, 2025 at 11:20 AM
access_denied on sign-in (oidc+spa app integration)

I integrated SPA authentication with Okta, after setting the sign-in URL and callback parameters, I try to access the application in question from the end customer dashboard or from the same local URL and I receive a 400 error describing a policy error and unknown identity provider, I do not have any IdP configured other than Okta, what could be the cause? Could it be an authentication policy different from the default catch?

/help/servlet/rtaImage?refid=0EMKZ000000dHrr

 

  • 2 answers
  • 250 views

  • joe.witt1.501629158262741E12 (Okta, Inc.)

    Hi @SergioM.66052 (Customer)​ . This is most likely a authorization policy issue. As a starting point, review your access policies under the authorization server being used by your application. If you are restricting access policies by application, this may be causing the error you are seeing. As @User17157611498146715886 (Customer Support Online Community and Social Care)​ has recommended reaching out the to Okta Developer Forum may also provide additional help on this topic. image

    Expand Post
    Selected as Best

  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hello @SergioM.66052 (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 similar post from Okta Developer: 

    OIDC 400 error on authentication,

    as well as this article:

    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.

    Expand Post

  • joe.witt1.501629158262741E12 (Okta, Inc.)

    Hi @SergioM.66052 (Customer)​ . This is most likely a authorization policy issue. As a starting point, review your access policies under the authorization server being used by your application. If you are restricting access policies by application, this may be causing the error you are seeing. As @User17157611498146715886 (Customer Support Online Community and Social Care)​ has recommended reaching out the to Okta Developer Forum may also provide additional help on this topic. image

    Expand Post
    Selected as Best
This question is closed.
Loading
access_denied on sign-in (oidc+spa app integration)