we are currently migrating to KNIME Server 4.13 and Executor 4.4.2 from an older version of both platforms and there seems to be a problem emerging with invoking remote workflow. To make this problem more comprehensive, here’s the intuition of my workflows:
- For the time being, I’ve got 2 Workflows A and B, both are deployed on the KNIME server. Workflow A requires users’ interactions and performs classic ETL. At the end, it would then pass some parameters to and invoke the second Workflow (Workflow B).
For this specific purpose, my workaround is to compress these parameters in a JSON Column and then pass the whole thing to the node “Call Remote Workflow (Row Based)” to call Workflow B using REST API. After providing the node with our server’s REST interface (something like https://xxxxxx:8080/knime/rest) and of course the necessary credentials, I clicked on the “List available workflows” and the node returned the “Could not list workflows: HTTP Status 403” error.
I assume it means access to the requested resource is forbidden. The server understood the request, but will not fulfill it. Since the invoking workflow works perfectly fine in the older server, I want to ask if there were any changes to the REST API interface or what could be done in this situation and how could we debug from the server side.