Sorry for any issues that you are having. Please visit https://wp-oauth.com and click on the icon in the bottom right of the page. This will open up a support ticket and allow you to contact us via the ticket system.
Thank you
Turns out the plugin was only deactivated somehow. What happened is that the update renamed the plugin folder so WordPress saw the previous one had disappeared and “deactivated” the plugin, but it did not automatically re-activate the newly installed one.
Is the latest version 3.5.7? I was hoping to check out the new authorization screen but I cannot seem to find it. Are you planning on implementing an admin page to de-authorize? and is there a way to revoke authorization from the client side?
Thank you for the support.
_wipes sweat from brows and breathes again_
I will have to check the plugin directory name issue. Yes, we have talked about adding an admin to de authorize tokens on the admin side. Currently, a client can de authorize by GET to /oauth/destroy?access_token=123. This will delete the client’s token and effectively de authorize the user and app until a new token is authorized.
My repo uses git, so file deletion is easy to spot and fix, so not too much sweat 🙂
Just noticed the changelog displayed through WordPress during updates is old, I was reading the 3.4.1 changelog notes:
= 3.4.1 =
* NEW: Added prompt parameter support for "login", "consent", and "none"
* NEW: Added User consent window for Authorization code flow.
* NEW: Added filter "wo_use_grant_request" to enable user consent dialog. Boolean.
So question: I use the Authorization code flow (I think), but I do not see any user content window. Am I supposed to see one?
Yes. If you use the prompt parameter and set it to either “login” or “consent” then there should be a prompt.
