It’s okay

I am sorry that you feel this way about the plugin. Please elaborate a bit more about the following statement.

the ONLY supported method is passing access token in a GET parameter

I am not aware of anything that this plugin has to do other than provide authorization to to WP REST API (authorize an access token). If there is something that you would like to see added to the OAuth2 side, please suggest it to IETF.

People are more than welcome to use OAuth 1 which is found by visiting https://github.com/WP-API/OAuth1. IT IS FREE. It is OAuth 1.0a which is not OAuth2 and thus anyone looking for OAuth2 SHOULD NOT use OAuth 1.0a.

I really wish you would of simply handled things a bit lighter and I would have been more than happy to bend the rules a bit.

Please keep this review based on the free version ??

I was referring to the fact that your integration with REST API was pretty much, non existent. The only support for REST API was passing token in GET parameter, but there’s no way I was going to tell all my clients they have to go through all their codebase and update all their API calls to put that in the GET parameter, because the pro version didn’t actually support the most popular method of OAuth2 which is something as simple as putting it in the header, and not in a GET parameter.

With that said, I see the plugin has been updated to support this, so even though this does not help me, hopefully it will help others who come across it

https://wp-oauth.com/kb/using-bearer-token-authorization/

I’ll make sure an update my review now that this is no longer an issue ??

• This reply was modified 8 years, 1 month ago by tripflex.