Summary
The user is facing issues with WooCommerce API authentication in the Airbyte connector, even though they were able to send a request successfully via exec into the server pod. The connector version being used is 0.5.
Question
Has anyone worked with the woocommerce api within airbyte? The current open source connector doesn’t seem to be passing the basic auth credentials correctly. I execed into the server pod and was able to send a request with a 200 response just fine, but connecting to woocommerce’s API within the UI doesn’t seem to work. I’m on the connector’s 0.5 version which I believe is the latest one.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["woocommerce-api", "airbyte-connector", "authentication", "pod", "ui", "connector-version"]
Just in case anyone else runs across this:
Woocommerce has a note from their <WooCommerce REST API Documentation - WP REST API v3 api page> saying:
Occasionally some servers may not parse the Authorization header correctly (if you see a “Consumer key is missing” error when authenticating over SSL, you have a server issue). In this case, you may provide the consumer key/secret as query string parameters instead.
I was able to get a 200 response by adding the cust_key and cust_secret to the stream parameter request vs. using the base_requester portion of the yaml manifest.
I’m not sure if this is just my instance of airbyte for some reason, but could be something to look into for the team developing this connector if they happen to read this.