I’m working on automating an internal API. Since we have everything on premise at this client and the API is documented with swagger, I thought the Web service would be a perfect fit.
I imported the JSON document, successfully generated the activities, tried a test run, and it doesn’t work.
Now, as you can see, it’s complaining about invalid credentials. The thing is, I don’t need to provide any to this API. It should be handled automatically being on the environment apparently, and I verified that it works due to trying it with the HTTP request activity, see the image below.
I’m not sharing the swagger document because I’m not sure I’m allowed to. My problem is that I am lacking information. I have some from the response, but I don’t know what request it’s making, so I don’t know what to change. My main question therefore is: how can I figure out what exactly the web service is doing?
I have done this with Wireshark in the past, but there are two main reasons I can’t use it here:
It’s being thoroughly blocked to install anything here that isn’t from the company store. Can’t even download portable versions.
It’s honestly way too much effort for something this simple.
Also, what’s up with the bearer token/Oath2token being marked as required even though they aren’t?
Studio version: 23.10.4
Windows VB Library
On premise orchestrator & studio
It might be quite tricky without having something like Fiddler installed to spy on the network and see exactly what is happening.
We will take this as a bug report, but I would suggest to simply go with the HTTP Request activity in this case. An alternative would be the Integration Service connector builder which also takes the swagger input and would be the modern approach to the issue:
Thank you for the response and putting the invalid required authentication through as a bug. I’ll make it work with the HTTP request for now.
I’m aware of the Integration service, but it’s only available in the cloud environment. As stated, I am (unfortunately) working for a client with an on premise installation at the moment.
Since the integration service can’t be used in every environment it would be nice to still get some love for the web service method, because that does work everywhere. But I shouldn’t have to use an external program to debug what’s going on…
As one more workaround, if you have a version that has the Coded Workflows:
Edit. Actually, it isn’t 100% match, sorry for that. I’ll leave it here anyway for some extra context though, because coded workflows might still be useful here anyway.
