04-27-2017 09:20 AM
I successfully exposed a process as a webservice.
The Rapidminer Server is running locally on my machine.
I can make a request to the webservice through Postman, or the browser and get the expected result.
But only when I try to call the webservice from my angular2 website,
because of a missing 'Access-Control-Allow-Origin'.
XMLHttpRequest cannot load http://localhost:8080/api/rest/public/process/applyDT. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access.
Where within the Rapidminer Server Settings can I setup the 'Access-Control-Allow-Origin' header?
I searched everywhere and couldn't find anybody with the same problem.
Any tips would be really appreciated.
04-27-2017 09:39 AM
The webservice is exposed as anonymous.
The process is stored at rapidminerserver/home/anonymous/...
I edited the access rights of the process, so that the anonymous user can do everything.
I query the webservice using the public link:
Thanks for your help,
04-29-2017 03:58 AM
Yes, i've already set both
Did not work unfortunately.
Thanks for your help,
05-02-2017 05:34 AM
This page gives plenty of information on the user anonymous and how to allow webservice access to this user.
05-04-2017 04:39 AM
I have read that documentation.
I followed it exactly as it is stated there.
The only thing that I was not able to follow was to give the anonymous user access rights to the webservice. In the documentation it says:
You can now set access rights to the web service.
User anonymous also has rights to the corresponding process and all linked content, such as data and models.
I can't find any option to edit access rights to the web service. I can only edit the web service or test it.
The only thing I was able to do, was giving the anonymous user access rights to the process/resource, which the web service is using.
05-07-2017 10:43 PM
I have the same Access-Control-Allow-Origin problem. Have you found the solution?
05-08-2017 10:00 AM
Sorry, but I misunderstood your problem in the first place.
As for now you cannot set the HTTP response header values (e.g. Access-Control-Allow-Origin) to enable CORS with RapidMiner Server.
We are aware of this and put in on our roadmap. Nevertheless, I am not able to make any assumptions regarding the solution date since changing this requires quite some effort.