We are trying to connect to Jira Software Cloud, which has a REST API. When I execute a request for the project list from Jira using https://<>.atlassian.net/rest/api/3/project/search, I get an empty array in the body of a valid response (200, “OK”). I have tried all possible combinations of Authentication on the REST Outbound Connector template (i.e., BASIC, OAuth, API Key) , but find that Camunda always returns an empty array for a response to a “GET” command for any API request on Jira that is supposed to return a JSON array. The servers are talking to each other and the GET request is valid and accepted, but the result is not what is expected. I have tested the exact same GET calls using various Jira user accounts (including a service account) and different authentication methods within the REST Outbound Connector template, but I still don’t get any data in the response array. I have cross checked it all with “Talend”, an API tester, to see if our GET call configurations would work properly there, and it does. The Talend correctly returns an array with content, whereas Camunda does not, using the same exact protocol and authentication method (Basic). So, it does not seem to be a problem on the Jira server side . Please let us know if anyone has any clues as to what might be causing this? I suspect that Camunda creates a curl request that might not be capturing the response properly. I did set up a “result” process variable to capture the response, that’s how I found the empty “” array in the body.
Hi @petercamunda, welcome to the forums! Definitely not the expected result of a REST call, and also the first time I’m hearing of an issue like this! Can you share a screenshot of how you’ve configured the REST connector, including the response/output variables? (Redact any keys/tokens of course!)