Hey Will,
The scenario is the following one:
- one private token to use the endpoint.
- one public token to use the application.
- Restrictions on using window.threekit.player.snapshotAsync() because this returns a base64 encoded image (Gmail doesn’t support base64 img)
Hence, the react application loads with the public token, when the user click an specific button it prepares the configurator to take the snapshot (i.e reset camera, change scene, change defaults, etc…) then it calls https://preview.threekit.com/api/asset-jobs/assetId/render/webgl/image API, this contains specific headers such ("authorization : Bearer XXX ") this one is private.
As a result I get CORS policy from server, and I am trying to solve this from client side, if it’s not possible I will have to run a node server in another site resolving it by server side.
Any suggestions?