Appearance
Cross-Origin Access (CORS)
About 885 wordsAbout 3 min
SettingsEmbeddedSecurity
2026-10-10
A browser lets JavaScript on one origin (scheme, host and port, such as https://app.example.com) call a server on another origin only if that server allows it with CORS response headers. These settings decide which origins Datafor allows and what they may send.
You need them when a page outside Datafor calls the Datafor server from the browser, most commonly the JavaScript SDK. A report shown in an iframe, a share link and XDM messages do not need CORS, because the report's own requests come from the Datafor page inside the frame.
Settings
Open Settings › Access & Integration › Cross-origin access (CORS). The settings apply to the current tenant.
| Group | Setting | Shipped value | What it does |
|---|---|---|---|
| Basic settings | Enable CORS | Off | While off, Datafor sends no CORS headers and browsers block calls from other origins. |
| Allowed origins | Empty | Origins allowed to call Datafor, written exactly as the browser sends them: scheme, host and port if it is not the default, without a path or trailing /, for example https://app.example.com or http://localhost:5173. Separate several origins with commas. * allows every origin; don't use it in production. | |
| Trusted domains | Empty | More origins, separated by commas, that are treated like Allowed origins while Enable CORS is on. Until 10.02 this field was on the Site address page; existing values were kept. | |
| Allowed methods | GET, HEAD, POST | HTTP methods other origins may use. Click Add, type a method and press Enter. | |
| Request and response headers | Allowed request headers | Content-Type, X-CSRF-Token | Headers other origins may send; click Add header to add one. Add Authorization for the SDK. If you remove every entry, Datafor allows whatever headers the browser asks for. |
| Exposed response headers | Empty | Response headers that scripts on other origins may read, for example Content-Disposition. | |
| Allow credentials | On | Lets the browser send and receive cookies on calls from allowed origins. While it is on, Allowed origins cannot contain *; saving shows "Allowed domains cannot be * when credentials are allowed. Enter explicit origin domains." |
Click Save. Discard changes restores the saved values.
You can enter Allowed origins one per line, as the hint says: saving turns line breaks and spaces into commas, also for Trusted domains. The server itself splits only at commas, so if you write the setting by other means, separate the origins with commas: https://app.example.com,https://portal.example.com.
How Datafor answers
When Enable CORS is on and a request carries an Origin header that is in Allowed origins or Trusted domains, Datafor adds to the response:
Access-Control-Allow-Originwith that origin, andVary: Origin;Access-Control-Allow-Credentials: truewhile Allow credentials is on;Access-Control-Allow-Methods,Access-Control-Allow-Headersand, if set,Access-Control-Expose-Headersfrom the settings above.
Datafor answers the browser's OPTIONS preflight requests itself with status 200. Requests from origins that are not allowed get no CORS headers, so the browser blocks them.
An origin in either list also gets a Content-Security-Policy header that names it in frame-ancestors, script-src, style-src and font-src, so a page on that origin can frame Datafor. This header is sent even while Enable CORS is off.
A request to a tenant address (/datafor/t/<tenant id>/…) is checked against that tenant's lists.
Set up CORS for the SDK
The SDK sends the embed token in an Authorization: Bearer <jwt> header. A cross-origin request with that header always triggers a preflight, so the server must allow both the origin and the header:
- Turn on Enable CORS.
- In Allowed origins, enter the origin of the page that hosts the SDK, for example
https://app.example.com. - In Allowed request headers, add
Authorization. KeepContent-TypeandX-CSRF-Token. - If the browser console reports a blocked method, for example while saving a report in edit mode, add it to Allowed methods.
- Click Save.
To check the result, send a preflight request from a terminal and look for Access-Control-Allow-Origin and Authorization in the response headers:
curl -i -X OPTIONS \
-H "Origin: https://app.example.com" \
-H "Access-Control-Request-Method: GET" \
-H "Access-Control-Request-Headers: authorization" \
https://bi.example.com/datafor/plugin/datafor/api/extension/auth/fetchUserTroubleshooting
| Browser console message | Likely cause | What to do |
|---|---|---|
No Access-Control-Allow-Origin header is present | Enable CORS is off, or the page's origin is not in Allowed origins exactly (different scheme or port, a path or trailing /) | Turn on Enable CORS and enter the origin as the browser shows it in the request's Origin header. |
Request header field authorization is not allowed | Authorization is missing from Allowed request headers | Add it and save. |
Method PUT (or another method) is not allowed | The method is missing from Allowed methods | Add it and save. |
| Calls work in one tenant but not in another | Settings, including Trusted domains, are per tenant | Repeat the settings in that tenant. |