brianlmerritt

Hey Paul – the connection does not use cookies. Either use basic auth for each request or use oAuth and token for each request.

ps to eastes! great! ps – make sure you use https for any basic auth requests for anything other than development. I developed my own auth plugin to save the mobile developers getting the full oAuth 1.0 working…

Hi vijjuxtra

Always post your request as a new one – you might get an answer that way ??

Also – you can test the api without coding – use Postman or Rest Client in your browser.

Closing issue – I am developing my own auth for the client.

Closing issue

Thanks – there are major concerns with opening up ANY meta data without analysis of what is already stored there (and repeat for every new plugin…)

The developer has to limit standard functionality of this plugin, particularly user and post meta.

OK ignore – the issue is performing a CURL via Rest Console (and probably Postman) from a browser already logged into WordPress.

By logging out, it works!

OK – sorry for the delay ??

Basic auth does work!

However, it fails if you are performing curl requests if you are already logged in on your browser and you are using Rest Console or Postman.

In other words, if you are running from a browser logged into your main site, and use a browser tool to curl for example, then it doesn’t work.

However, once you log out of the browser then basic auth takes over and works fine ??

ps – If you find a fix, please do repost here ??

Basic auth appears to NOT sign the user into WordPress, and is just used to get the user ID.

I believe only OAuth currently supports post and user edits, but as I don’t personally like 3leg OAuth 1.0a (not for mobile apps), I have not investigated further.

So unfortunately you can believe your curls are all wrong and yet it appears basic auth released plugin does not support writing.

You might want to shunt over to git-hub and see if there are updates there or do like I am doing and creating my own routes and endpoints and auth because in fact the one thing I don’t need to do is access users, posts, or media for my app ??

No worries! I am NOT going ahead with 3 legged OAuth 1.0a, and am working on wordpress user login via basic auth combined with generating keys for the user using a modified version of key auth.

That seems to be working, so the focus now is on building routes and endpoints into my WordPress app and hooking all this into the mobile app…

Sorry, the error I get is:

[{
    "code": "json_cannot_edit",
    "message": "Sorry, you are not allowed to edit this post."
}]

It looks like you are using your own code again.

Use OAuth Explorer to generate a good link and then you can replicate that.

If you are using OAuth Explorer and getting an error then there is still an error in your configuration because it just works as I described it.

I am not likely to get any support from the team with your comments here @horatiub so put ALL of the details of how far you have got and please start your own thread and don’t jump onto other ones unless you are adding a fix…

That is what the instructions say…

ps – are you/your host company changing directory to the actual wordpress root folder?

cd /var/www/wordpress or whatever before running the wp command?

https://wp-cli.org/ may help