403 Error is thrown after typing in Username on a CORS enabled realm

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All


    At first the SecureAuth realm loads fine but when the User types in their Username, they then see a 403 instead of the multifactor methods page. 

    Clicking on the Address bar and hitting Enter (to reload the page) successfully loads the MFA page.



    CORS has been configured for this realm with failUnlistedOrigins=”true”

    The origin is not in the list of origins and so CORS throws a 403



    Use the Browser Dev Tools to check what the origin is when you see the 403. We often see that it is the address of the SecureAuth server that is throwing the 403 Eg Https://sa.example.com 

    Add a CORS entry to the web.config for this origin and it should fix the issue.



    <cors enabled=”true” failUnlistedOrigins=”true”>
    <add origin=”https://sa.example.com” >





    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.