06-16-2021 02:16 PM
I am developing a small utility to help manage agent attributes using the UCCE Config Agent API. The node server vends an HTML single-page app that assembles the request and then fires it to the selected UCCE AW.
I am getting the following response when attempting to test:
Access to XMLHttpRequest at 'https://awhost.co.com/unifiedconfig/config/agent/15194' from origin 'https://localhost:5020' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
I'm curious if this is a known issue (e.g., these API's must be run from PostMan) or if it is a side-error of some other fixable problem (maybe my credential is being rejected?). Has any one experienced this? Or accomplished what I'm trying?
Thanks,
Chris
06-17-2021 06:50 AM
You have to enable CORS on Tomcat. I think the file is called web.xml or web.config or maybe both. I thought I had it documented it somewhere, but I can't readily find it.
david
06-17-2021 09:30 AM
Hi,
I don't believe that the UCCE APIs support CORs. Finesse APIs do and there is a CLI for that. I don't see anything in the CCE developer guide that states that CORs is supported and doesn't mention anything about OPTIONS.
Thanx,
Denise
06-17-2021 11:02 AM
Is this what you're running into?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide