Access to XMLHTTPRequest has been blocked by CORS policy

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth version affected: All


    Access to XMLHTTPRequest has been blocked by CORS policy. Request Header Field tokenid is not allowed by Access-Control-Allow-Headers



    HTTP Response Headers in IIS are restricting  this.



    Check that the Field mentioned in the error above (In my example, tokenid) is a header that you wish to allow. If so, edit the Response Headers to allow it. 

    1. Open IIS
    2. Navigate to the realm
    3. Double click on the HTTP Response Headers option
    4. Add

    In my example, I am specifically setting tokenid

    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.