If you have a CORS error you must contact your System Admin or Integration provider. They will then check if your system is CORS compliant.
For more Information, here is a section from Integration Partner Onboarding Document Page 16:
"Your System needs to support CORS to work with different Hostsystems (eg. Adobe CEP 11 and above). Adobe has rolled out new Creative Cloud Applications and now REQUIRES that Plugins are CORS (Cross-Origin-Resource-Sharing) compliant.
We have prepared more info for you to understand the issue:
CI HUB Connector is an HTML/CSS/JS-based Single Page Application (SPA).
The CI HUB Connector is obtained from the domain ci-hub.azurewebsites.net (LIVE), and ci-hub-test.azurewebsites.net (STAGE), the content (data and assets) of other systems (DAM, PIM, ...) always comes from another source (Origin)
The underlying browser enforces a check for these accesses due to the Same Origin Policy (SOP), whether the “other” side agrees to a Cross-Origin Resource Sharing (CORS) access.
This means for our partners and their API:
Each API endpoint must support the CORS protocol, specifically:
- Support for OPTIONS requests
- Support for the request header “Origin” and the corresponding response header “Access-Control-Allow-Origin”.
- Support of “Access-Control-Request-Method” and “Access-Control-Allow-Methods
- Support of “Access-Control-Request-Headers” and “Access-Control-Allow-Headers"
The host applications like PowerPoint, Word, Excel, Outlook have always performed the CORS
checks. What is new is that Adobe products such as InDesign, Photoshop, Illustrator, Premiere Pro,
After Effects are now gradually being migrated to CEP 11. In CEP 11, CORS checking (previously
disabled) has been enabled, meaning ALL host applications supported by the CI HUB Connector,
require a CORS-compatible API from you.
So far, we have always checked the CORS compatibility of the partner systems provided to us during
the development of the Content-Integration, possibly pointed out problems to the partners or
implemented our workarounds. However, we cannot ensure that other partner systems unknown to
us (e.g., On Premise instances) also meet the CORS criteria.
Unfortunately, the feedback from the browser on CORS violations is extremely low,
Therefore, CORS errors only show up in the direction of the CI HUB Connector with the error
message: “Network error.” (There is more information in the Debugger Console, but it is not
available for the CI HUB Connector).