Automatically closed - issue fixed for 2 weeks with no activity.
This problem might be related to a new version of Zammad 3.4.
Articles (which will be treated as comments in Drupal) are not fetched anymore. The request results in an "unauthorized" error.
You can execute the following curl:
curl -H "Authorization: Token token=<your_token>" -H "Content-Type: application/json" -H "X-On-Behalf-Of: 14" -X GET https://zammad.test.bitegra-solutions.de/api/v1/tickets/
This works fine. But if you want the corresponding articles of a ticket:
curl -H "Authorization: Token token=<your_token>" -H "Content-Type: application/json" -H "X-On-Behalf-Of: 14" -X GET https://zammad.test.bitegra-solutions.de/api/v1/ticket_articles/by_ticket/12
Result: {"error":"Not authorized","error_human":"Not authorized"}
The API token has all available permissions.
You have to leave out the On-Behalf Header.
The php client we use in Drupal, uses the same request, so it does not work there either, because we set the On-Behalf.
I think, this makes no sense in the Zammad API, if the problem is not somewhere else.
To fix this on our side, there is a function unsetOnBehalfOfUser
we can call before we fetch articles. This works.
Fixed
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Automatically closed - issue fixed for 2 weeks with no activity.