v3 API still sometimes errors on authentication over SSL about wc-api-ruby HOT 5 CLOSED

Index works because don't need any authentication.

To V3 is not possible to pass keys as query string, I recommend you use oAuth in this case.
Maybe we can do something to force use oAuth even when the URL is over SSL.

from wc-api-ruby.

Hmm, the query string is working for me on woo 2.4.7 with v3 passed into the client gem.

Will oauth work even if it's https? Should we make an option to force oauth in the gem?

from wc-api-ruby.

Yep, oAuth can work with https and yep, I agree, will be great have some option for it.

And sorry, I had misunderstood:

It does work if I include the secret and key in the query params.

The problem is the server unable to configure PHP_AUTH_USER and PHP_AUTH_PW.

Here how this works: https://github.com/woothemes/woocommerce/blob/master/includes/api/class-wc-api-authentication.php#L79-L93

See that we test for the query strings first as fallback and then we try PHP vars.

from wc-api-ruby.

@claudiosmweb

Thanks for sending me the link to the location in woocommerce code that this relates to. It looks like woo never tries to do oauth over ssl:

https://github.com/woothemes/woocommerce/blob/master/includes/api/class-wc-api-authentication.php#L45-L49

I have a change on my fork that will allow a client to always use oauth but I don't think that will work until ssl is able to read the oauth params.

from wc-api-ruby.

Closing since need to use Basic Auth over SSL.

from wc-api-ruby.