Hey guys,

Just wondering if this plugin is supposed to work with WP 4.4. Seems like it has not been updated for a while, one filter has changed and by trying to debug it I feel like it is not mean to work with the latest version of WP. I might be wrong but I want to make sure. Thanks!

…mmit makes it so it also shows an error like it did with wp api v1. Because currently if you're using this plugin with WP API v2, it mostly works. Except if you provide a bad username and password combination, there is no error message like there was working with wp api v1. This can be troublesome if, for example, logged in admins can see all users, whereas someone who's not logged in can only see a subset.

1. Basic auth doesn't work by direct url in browser (try url like http://wp.lo/wp-json in browser)
2. Basic auth doesn't work for wp api v2 (https://github.com/WP-API/WP-API) in cases:

• curl -i --user user:pass http://wp.lo/wp-json/
• curl -i --user not_exists_user:pass http://wp.lo/wp-json/
• curl -i http://wp.lo/wp-json/

addresses #12 in WP-API/Basic-Auth. Just required that the basic-auth take a stab at finding the current user, and if it does find the current user, then it we shouldn't have the cookie method try finding the current user separately (where it would overwrite what we've found). I've been using this while logged into my browser and using basic auth.

Basic Auth is mentioned as a way to authenticate on http://v2.wp-api.org/guide/authentication/, and it's mentioned that you should be able to discover what authentication methods are available on http://v2.wp-api.org/guide/discovery/. So should the basic auth plugin add an entry into the index's "authentication" response property? It seems to me like it should (and I'm happy to make a pull request)

Since upgrading to 4.7.2 any post requests to the site trigger a 401 response. I have noticed others having the same issue. Has this plugin been abandoned?

{
  "code": "rest_cannot_create",
  "message": "Sorry, you are not allowed to create posts as this user.",
  "data": {
    "status": 401
  }
}

Problem

http://wpackagist.org/ is modernizing how we control our plugins via composer. As such, I think it would be beneficial to allow this plugin to be downloaded from wordpress.

I'm sure this was considered but perhaps put off due to specific needs. I just want an issue revolving around this particular subject.

Discussion

I did circumvent the need by adding composer-installer to this module #19 . By doing so, we give control to the project owner to define where they want basic-auth to install to. That is a custom plugins folder.

If basic auth is used, we need to return null for json_basic_auth_error. Right now, if basic auth isn't used, we just assume the user is authenticated even if no authentication method has been used.

To confirm this bug, view /posts/?context=edit (without sending a nonce) while the Basic Auth plugin is enabled. You will see posts when you shouldn't.

The request returns the following when base64 encoded Authorization is sent:

{
"code":"json_not_logged_in",
"message":"You are not currently logged in."
}

I updated the wordpress to new version and basic auth doesnt working anymore

im using basic auth and this headers: Authorization => Basic base64_encode(username : password)

Im reciving unauthorized response

Hello, I've been trying to make a basic auth for a custom route that I made but couldn't find how to do so.

Here's my code:

function AllPostsByDESCDate( $data ) { $posts = get_posts(array( 'posts_per_page' => 10, 'paged' => $data['paged'], 'orderby' => 'post_date', 'order' => 'DESC', 'post_type' => array( 'post', 'page', 'custom-post-type' ), // custom post types 'post_status' => 'publish', 'suppress_filters' => true ));

if ( empty( $posts ) ) { return null; }

return $posts; }

I can send a get http request without Basic Auth while sending an http request to wp-prefix/v2/posts requires me to Basic Auth.

register_rest_route( 'wp-prefix/v2', '/AllPostsByDESCDate/(?P[a-zA-Z0-9-]+)', array( 'methods' => 'GET', 'callback' => 'AllPostsByDESCDate' ) );

I'm using REST API TOOLBOX (https://he.wordpress.org/plugins/rest-api-toolbox/) to choose which endpoint requires an auth

i try {{site}}/wp-json/wp/v2/posts/24?content=long_text_url_encode

why got error 414 Request-URI Too Large The request URL is over the maximum size allowed!

can you give me solution? thanks

Trying WP API by Nodejs by Axios but getting Authentication issue

curl -i  -X POST \ -H --user admin:pass -H "Content-Type: application/json" -d '{"title":"POST TWO","content":"Two","status":"publish"}' http://www.test.localhost/?rest_route=/wp/v2/projects

Code in Image

const express = require("express")
const axios = require("axios")
const app = express()
axios.defaults.baseURL = 'http://www.test.localhost/?rest_route=';
app.get("/",(req,res)=>{
	axios({
		method:"POST",
		headers:{
			'Content-Type': 'application/json;charset=utf8',
      		'Authorization':'Basic YWRtaW46cGFzcw=='
  		},
		url:'/wp/v2/projects',
		data:{"title":"POST three","content":"Two","status":"publish"},

	}).then(data=>{
		res.send(data)
	}).catch(err=>{
		console.log(err)
		res.send(err)
	})
})
app.listen(8000,()=>{
	console.log(`localhost:8000`)
})

working on CURL

working on POSTMAN

Getting this error

TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'ClientRequest'
    |     property 'socket' -> object with constructor 'Socket'
    --- property '_httpMessage' closes the circle
    at JSON.stringify (<anonymous>)
    at stringify (/home/tech/Desktop/Project/role/node_modules/express/lib/response.js:1128:12)
    at ServerResponse.json (/home/tech/Desktop/Project/role/node_modules/express/lib/response.js:260:14)
    at ServerResponse.send (/home/tech/Desktop/Project/role/node_modules/express/lib/response.js:158:21)
    at /home/tech/Desktop/Project/role/index.js:18:7
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

No matter what I try I can't complete troubleshooter for AppMySite as it says "Your WooCommerce Consumer Key and Consumer Secret are not authorised." How does it authorise?

Hi all, I am on the latest wordpress version so this may be the issue, however I get an recaptcha error every time I try to use Postman to log into to upload images.

Here is the return when I use basic auth as the authorization. { "code": "recaptcha_error", "message": "<strong>The reCAPTCHA wasn't entered correctly. Please try it again.</strong>", "data": null }

What could I do?

I have implemented this plugin. It works great for non logged in user but for logged in user used via Postman, it shows the following. Could you please help solve this. I have latest wordpress install till date.

Login Warning There was an issue with your log in. Your user account has logged in recently from a different location.