nickb

Excellent! Now I have a plan!
Thanks a lot for your help.

I agree that 277 is too many… I was also thinking about some sort of drill down filtering as the user types in.
I could transfer the 277 words at once, through one specific endpoint, as a matrix… It should not be too big and that would limit the overheard that I would get from sending 277 individual options. The app would implement the drill down filtering and the list would not need to be hard coded in the app.
I could pre-load the same list into a WP custom taxonomy in the backend, to capture and store the selection of the user.

Thanks a lot!
Sorry my question was not very clear… The user needs to select one option in the app, out of the list of 277, and the app will send that option to WP. I am trying to use the REST API to pass the list of the 277 options to the app, in case that list changes in the future.
I will create a custom route to send the list of options to the app or code the list in the app. I’ll use SQL for all other actions when I have received the value.

not working for me either…

@trevorwood Great! Thanks a lot for the quick reply!

@trevorwood I am having the same issue. Did you find a way to resolve it?

@napolux, did you find a way to implement social login for the REST API?
I am using WP OAUTH Server for existing users and it is working well. But I would like to offer social login for new members. We use WordPress as a headless CMS and do everything through the API from a mobile app.

Any thoughts would be great!

I have not found any simply way to add or delete one field in the array, so I guess I need to GET the full list of users, then add or delete one of them, then POST the full updated list back.

Is this my best option?

Thanks!

Hi Justin,

It works well now. I still use basic auth for the client_id and client_secret.
I added a param ‘content_type’ of ‘application/json’ in the header which seems to have make the difference.

Thanks a lot again for your great support!

Hi Justin,

Thanks again for the support.
I did try again with the “/” after the sub-directory, but got another error:

{
  "error": "invalid_client",
  "error_description": "No client id supplied"
}

I sent:

POST /wordpress/?oauth=authorize HTTP/1.1
Host: localhost:8080
Authorization: Basic dkVpQ0t4VVZCVGtMUTFkV0JSRWR0VDU2QmV5UkwyOjg2ZW1qWlpIWVJDbkF4THRjRjJiZWZJQzh5a3d4MA==
Cache-Control: no-cache
Postman-Token: 45ee3728-60ae-c945-7e0a-f0eddae9b8af
Content-Type: application/x-www-form-urlencoded

grant_type=password&username=xxxxxxxxx&password=xxxxxxx

I need to redo a clean installation of wordpress and start from scratch.

Thanks.

Hi

I tried deleting everything from the .htaccess file but it did not help: Still having the same issue.

I also tried the password grant type (I purchase a full license), using a real username and password, but got exactly the same error . This is the log from postman

POST /wordpress?oauth=token HTTP/1.1
Host: localhost:8080
Authorization: Basic dkVpQ0t4VVZCVGtMUTFkV0JSRWR0VDU2QmV5UkwyOjg2ZW1qWlpIWVJDbkF4THRjRjJiZWZJQzh5a3d4MA==
Cache-Control: no-cache
Postman-Token: fc833b5b-dfe2-1530-3283-0e609bc4ae16
Content-Type: application/x-www-form-urlencoded

grant_type=password&username=xxxxxx&password=xxxxx

Any thoughts?

Thanks

I am up-to-date running WP 4.5.2.

I tried todd-activate all plugins but it did not help. Could it be linked to an issue with the header?

Thanks

I am using permalink for WP REST and a local implementation: https://localhost:8080/wordpress?oauth=token

Could this be the issue? What should I try?
Thanks

Hi,

I am having the same issue a POST to WP OAUTH SERVER returning:
{
“error”: “invalid_request”,
“error_description”: “The request method must be POST when requesting an access token”,
“error_uri”: “https://tools.ietf.org/html/rfc6749#section-3.2”
}
when I am sending a POST in Postman.

I modified my .htaccess to be the same as the bottom of: https://wp-oauth.com/2016/01/cors-preflight-requests-issues/

I am using version 3.1.x of the plugin (will update to 3.2),
In Postman I am passing the client ID and secret in Authorization, with a grant_type of authorization_code in the body.

I am running wordpress on localhost. I can use WP REST with basic authentication and with Oauth1.0a – except for OPTIONS and filters.

Any idea?