Unable to use REST API to start workflow since upgrade to vCO 6.0.0

[MikaelPareChabo]

I updated my vCO to 6.0.0. I'm no longer able to do GET or POST to run my workflow. When I'm browing to "https://{IP/Hostname}:8281/vco/api/workflows", I can't get anything anymore.

Does someone have any Idea ?

[Burke-]

We'll need more info to help...

What client are you using to attempt access to the REST API? (I have a good tutorial here: http://bit.ly/restvco )

can you access https://<your-vro-server>:8281/vco/api/docs ?

[MikaelPareChabo]

Hi Burke,

I followed your turtorial and it was working well before I did the upgrade. I'm currently using "Rest Advanced Client" in Chrome. And yes I'm able to access https://<your-vro-server>:8281/vco/api/ and/or https://<your-vro-server>:8281/vco/api/docs

[Burke-]

Not sure what to say here, I just tested using the RESTClient in Firefox and simply using Firefox directly - in both cases, my vRO 6.0 server responded with a list of workflows.

Perhaps someone else here has a similar experience or a better idea of what to look at.

[iiliev · Accepted solution]

/vco/api/ and /vco/api/docs/ allow unauthenticated access whereas /vco/api/workflows/ requires authentication. Perhaps "Rest advanced client" or Chrome itself are trying to use some cached credentials (or other cached stuff).

Could you open a new incognito window in Chrome (Ctrl+Shift+N) and try with the /vco/api/workflows/ URL directly in the Chrome URL bar (without Rest advanced client) to check if the request will ask for credentials and return list of workflows?

An alternative would be to try with a command-line REST client, like curl or similar.

[MikaelPareChabo]

Thank you Ilian Iliev, it worked with the incognito window. So it was cached credentials that were wrong. I attachedto my domain just after the upgrade. Didn't tought it could be the problem.

Thanks !