I have created triggered task in cloudplex which is tested & working from postman but the same is not working from javascript. Just want to know if any one done any setup for Cross Origin Request Sharing (CORS) in snaplogic cloudplex
Yes I have read the documentation & configured accordingly Now its working fine 🙂
Hi @tlikarish,
your solution works, thank you so much!
Have you checked out the documentation on Triggered Pipeline Access Control? Let us know if there are gaps or more details that we could provide.
Hi, tlikarish,
I faced with the same CORS issue as described above.
I have a triggered task, which is requested from another domain in JavaScript with the XMLHttpRequest object.
I use the cloud URL, the Snaplex is set to Cloudplex, the CORS allow list contains the domain the request is coming from, but it still doesn’t work.
First attempt with .*msgfocus.com as in documentation
Second one with *.msgfocus.com
In all cases there is an error
It is also stated in the documentation: " Contact SnapLogic Support to configure this setting."
Possibly there is something else to do to enable this option?
Thank you,
Vitaly Chupaev
It seems your request is not simple, so a preflight OPTIONS request is being sent first to see if it’s safe to send. The Authorization header may make it non-simple. Anyway, you’re failing on this request.
In your first experiment, did you try an explicit origin (that is, no * wildcard). It looks like it, but want to verify.
I think you should be ok going from HTTP → HTTPS.
The error message in your screenshot says No Access-Control-Allow-Origin header is present on the requested resource for the preflight request. It seems something is missing in the request.
This article touches on how to avoid preflight and other thing to check for – it’s pretty good.
Hi, @mbowen,
yes the request sends the Authorization header, since it is a call to the SL task, which requires a token, so looks like I cannot avoid a preflight call.
I tried a host without asterisk, actually I have both records at the same time - with full domain and with wildcard.
Actually I expected that after setting the Allowlist I will have Access-Control-Allow-Origin header in response.
I want to understand where is a problem, I can think about these reasons:
Thank you.
