woocommerce_api_authentication_error","message":"Consumer Secret is invalid

[chbichsel]

When using HTTPS in the API URL parameter below the authentication fails with the error"

"woocommerce_api_authentication_error","message":"Consumer Secret is invalid".

HTTP works fine.

Questions:

• Any suggestions on how to troubleshoot this?
• If this is a potential server side configuration issues, do you have any pointers on how to configure it correctly?
• Could you give me an example of how to use query parameters instead? The WooCommerce REST API documentation hints at an example for servers that not properly parse the Authorization header, but it is actually missing.

API(
            url="https://kashalife.net/",
            consumer_key   ="ck_16c59a1a0693c2723928830da52a30640c2311fd",
            consumer_secret="cs_0b4e0f17741e024b31d0ef799257b972db473305",
            wp_api=False,
            verify_ssl=False,
            version="v3",
        )

Thanks - Christoph

[claudiosanches]

Maybe it's your server's configuration. Have you saw our docs?

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.

You can test using cURL:

curl -k -u consumer_key:consumer_secret https://www.example.com/wp-json/wc/v1/orders

And

curl -k -g "https://www.example.com/wp-json/wc/v1/orders?consumer_key=123&consumer_secret=abc"

[chbichsel]

Hi Claudio,

Thanks for your reply! Before posting this questions I have been trying for 5+ days to figure this out by myself by using documentations from woothemes, woocommerce, and any other info on google. The fact that I have not been able to resolve the issue, and have not found a lot of detail on it, tells me that I am either searching for the wrong things , or that it is so obvious for people who understand basic auth over https and webserver configurations that its just a no brainer (for them).

Two questions:

1. Thanks for the curl commands. Auth with ULR params works with my server, but not headers. I haven't tried "Websites behind load balancers or reverse proxies" of the WooThemes SSL and HTTPS documentation. I'll do that next. Any other pointers to what configuration may be wrong?
2. URL params auth is not natively supported in the python wrapper, correct?

** Header auth wc-API (fails)
url -k -u ck_6beecb5aad00b590d8e69d23ccf59773d002f6e5:cs_e6ba5dbce62af9c0f92ebbaa78557177135688de https://kashalife.net/wc-api/v3/products/

* Header auth wp-JSON (fails)
curl -k -u ck_6beecb5aad00b590d8e69d23ccf59773d002f6e5:cs_e6ba5dbce62af9c0f92ebbaa78557177135688de https://kashalife.net/wp-json/wc/v1/products/

URL PARAMS wc-API (ok)
curl -k -g "https://kashalife.net/wc-api/v3/products/?consumer_key=ck_6beecb5aad00b590d8e69d23ccf59773d002f6e5&consumer_secret=cs_e6ba5dbce62af9c0f92ebbaa78557177135688de"

URL PARAMS wc-JSON (ok)
curl -k -g "https://kashalife.net/wp-json/wc/v1/products/?consumer_key=ck_6beecb5aad00b590d8e69d23ccf59773d002f6e5&consumer_secret=cs_e6ba5dbce62af9c0f92ebbaa78557177135688de"

[claudiosanches]

URL params auth is not natively supported in the python wrapper, correct?

No yet, I added support for it in our other wrappers, you are the first person that ask for it.
I'll add support for it today, by the end of the day you'll be able to update and use it as query strings :)

[chbichsel]

Wow, great! Thank you Claudio!

From: Claudio Sanches [mailto:notifications@github.com]
Sent: Wednesday, June 22, 2016 11:20 AM
To: woothemes/wc-api-python wc-api-python@noreply.github.com
Cc: chbichsel chbichsel@msn.com; Author author@noreply.github.com
Subject: Re: [woothemes/wc-api-python] woocommerce_api_authentication_error","message":"Consumer Secret is invalid (#16)

URL params auth is not natively supported in the python wrapper, correct?

No yet, I added support for it in our other wrappers.
I'll add support for it today, by the end of the day you'll be able to update and use it as query strings :)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/16#issuecomment-227832470, or mute the threadhttps://github.com/notifications/unsubscribe/AR4SzVl57uNrgdvG4j9rzUX0-PPzMDbbks5qOXzYgaJpZM4I7dND.

[claudiosanches]

@chbichsel Solved in version 1.2.0, now you just need to update and set your wrapper using the query_string_auth option, see example:

API(
    url="https://kashalife.net/",
    consumer_key="ck_16c59a1a0693c2723928830da52a30640c2311fd",
    consumer_secret="cs_0b4e0f17741e024b31d0ef799257b972db473305",
    wp_api=False,
    verify_ssl=False,
    version="v3",
    query_string_auth=True
)

[chbichsel]

Sweet. Thanks!

From: Claudio Sanches [mailto:notifications@github.com]
Sent: Wednesday, June 22, 2016 4:35 PM
To: woothemes/wc-api-python wc-api-python@noreply.github.com
Cc: chbichsel chbichsel@msn.com; Mention mention@noreply.github.com
Subject: Re: [woothemes/wc-api-python] woocommerce_api_authentication_error","message":"Consumer Secret is invalid (#16)

@chbichselhttps://github.com/chbichsel Solved in version 1.2.0, now you just need to update and set your wrapper using the query_string_auth option, see example:

API(

url="https://kashalife.net/",

consumer_key="ck_16c59a1a0693c2723928830da52a30640c2311fd",

consumer_secret="cs_0b4e0f17741e024b31d0ef799257b972db473305",

wp_api=False,

verify_ssl=False,

version="v3",

query_string_auth=True

)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com//issues/16#issuecomment-227908665, or mute the threadhttps://github.com/notifications/unsubscribe/AR4SzYKP-Bus8kZ1AMk94IJ8Uu6_yDcJks5qOca7gaJpZM4I7dND.