sleuthbuilder

@contactjavas I’m curious, the docs mention passing the username and password as a parameter – isn’t that normally considered a query arg or am I misunderstanding?

To generate token, submit a POST request to this endpoint. With username and password as the parameters.

Your mention of including it in the body helped me with my issue. Am I misunderstanding how this works or is there more to it?

I’d also like to know what an appropriate Nginx rule would be. I currently have this in my Nginx configuration and had no issues generating a token using Postman.

#JWT Auth plugin
if ($http_HTTP_JWT_AUTHORIZATION ~ "^(.*)"){
	set $rule_0 1;
}
if ($rule_0 = "1"){
	set $http_HTTP_JWT_AUTHORIZATION %1;
}

This is another Nginx rule that was suggested by a colleague of mine.

if ($http_authorization ~ "^(.*)"){
	set $rule_0 1;
}
if ($rule_0 = "1"){
	set $http_authorization %1;
}

@rawkus2g

I can’t guarantee it will work but it’s worth a try and has worked so far on a test site I’m using.
If you have access to phpMyAdmin (or something similar) you can run this query for your database after selecting your database name. You will also need to replace wp_options with what you have set in your table_prefix in wp-config.php.

Example, if you have raw_ in your table_prefix, you’ll have to run this query instead (I replaced wp_ with raw_).

SELECT * FROM raw_options WHERE option_name = 'wc_remote_inbox_notifications_specs'

I hope this helps!

One thing that I am seeing when running a trace on a request like this is that there’s a request to 192.0.66.5 IP and an update to the table wp_options using an INSERT INTO statement.

This option is constantly updated wc_remote_inbox_notifications_specs in a never-ending loop.

It seems that setting this option’s “autoload” setting to “no” fixes product updates.
Updating Woo’s database doesn’t help either.

I used this query to pull the option from the database:
SELECT * FROM wp_options WHERE option_name = 'wc_remote_inbox_notifications_specs'

Then I updated the “autoload” setting to “no” from “yes”.

• This reply was modified 5 years, 4 months ago by sleuthbuilder.