I've created an HTTP target extension with the following details:
Content type: JSON
Basic auth: Enabled
Password: My API token
Now the first time I set it to test target and hit submit it works just fine, and I get a HTTP/1.1 200 OK response.
The problem is, once I create the HTTP target, and go back into it and try and test it again, I get HTTP/1.1 401 Unauthorized.
When I look at the request headers, the Authorization header is different for both requests. The second failing request's decoded auth header doesn't contain a password, just the username. The first successful request's auth header contains both a username and password.
The real problem is that when I run this extension in an automation, it's failing, and I suspect it's failing because it's messing up the authorisation and not sending the password properly, however there is no way to know.
Any idea's on how to solve this? I'm 100% sure it's a bug, but Zendesk has no bug reporting system.
Please sign in to leave a comment.