Expiry is not 3600s !

Hi,

This typically happens when the server times do not match WP times. A token will appear to expire early or to never have been valid in cases like this.

Please check to ensure, PHP time is the same as WP time.

@justingreerbbi

It seems that’s the cause, timezone in WP is different than my system’s (my system, because I’m building a desktop app).

How do I protect the plugin if I buy “Unlimted Sites” edition? I need to install this on client’s websites to activate REST API functionality.

Thanks a lot

Good to hear you found the issue!

Support for this plugin does not extend to 3rd parties but you can add the plugin internally to your plugin as a vendor. I will not provide support for this but I will say it is possible. You will be responsible for updating the your plugin and packages in your plugin.

Put WP OAuth Server into your plugin /your-plugin/vendors/wp-oauth-server. From there you can require the main file and need to call the install and setup functions inside your plugins activation hook. This will inturn activate WP OAuth Server and run under your plugin.

Again there is no support for this from us but we can help you with your specific instance. Every time there is an update from us, you will be responsible for implementing the update into your plugin and testing.

I hope this makes some sense.

Thank you, I understand and appreciate your help.