This article will help you configure Seeq to allow a third party web application to access the Seeq REST API from the browser.
By default, modern browsers disallow most HTTP requests to domains other than the domain from which the web application was served (i.e. cross-origin requests). HTTP requests to other domains can be enabled by configuring CORS. Lean more about CORS at:
The "Network/Http/AllowedOrigins" setting is a string value that specifies which remote origin(s) are allowed to make cross-origin requests to the Seeq server.
This setting is managed by Seeq and cannot be changed by customer administrators. If you need this setting changed, contact Seeq Support.
Allowed origins effectively extend the Seeq security perimeter. Any code running on an allowed origin can make any authenticated read or write API request that the signed-in user is authorized to make. Only specify origins that are fully trusted and protected against risks such as XSS and supply-chain compromise.
-
If the setting is not configured, then no cross-origin requests are allowed.
-
The value may be set to a single remote origin.
https://somesite.com
-
The value may be set to a comma-separated list of remote origins that are all allowed to make CORS requests to the server.
https://somesite.com,https://someothersite.org:8080
Note: the port should not be specified if it is the default port for the service requested (e.g. port 80 for http, or port 443 for https).