Title: It’s okay
Last modified: February 16, 2017

---

# It’s okay

 *  [tripflex](https://wordpress.org/support/users/tripflex/)
 * (@tripflex)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/rest-api-beware/)
 * Purchased pro version before header support was added for REST API so had no 
   use for it, but since that time support has been added, and this review was updated
   to remove the 1 star
    -  This topic was modified 9 years, 3 months ago by [tripflex](https://wordpress.org/support/users/tripflex/).

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Justin Greer](https://wordpress.org/support/users/justingreerbbi/)
 * (@justingreerbbi)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/rest-api-beware/#post-8118291)
 * 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](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 😉
 *  Thread Starter [tripflex](https://wordpress.org/support/users/tripflex/)
 * (@tripflex)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/rest-api-beware/#post-8810678)
 * 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/](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 9 years, 3 months ago by [tripflex](https://wordpress.org/support/users/tripflex/).

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘It’s okay’ is closed to new replies.

 * ![](https://ps.w.org/oauth2-provider/assets/icon-256x256.gif?rev=2603051)
 * [WP OAuth Server (OAuth Authentication)](https://wordpress.org/plugins/oauth2-provider/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/oauth2-provider/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/oauth2-provider/)
 * [Active Topics](https://wordpress.org/support/plugin/oauth2-provider/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/oauth2-provider/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/oauth2-provider/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [tripflex](https://wordpress.org/support/users/tripflex/)
 * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/rest-api-beware/#post-8810678)