• jalokim

    (@jalokim)


    Hi.

    I updated your plugin yesterday to version 1.2.5 and I can no longer POST requests.

    I have a custom post type and custom user role that serves only to save data to this custom type. everything works great prior to 1.2.5

    Now I keep getting error 401, rest_cannot_create and that my user hasn’t got sufficient rights. JWT token is ok and valid, JWT token is attached to bearer in headers. I even changed the user rights to admin and same 401 problem.

    Reverted to version 1.2.3 and everything works perfectly.
    Any idea what happened in the new version that I am no longer authenticated?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Goran87

    (@goran87)

    Same here.

    One strange this is that its working when testing with Postman, but not working when I am using javascript fetch. It was working with 1.2.4, I rolled back and all good, I suppose we are missing some additional data to pass?

    guntercn

    (@guntercn)

    hi, i think i got the same error.
    my site is:
    WP: 4.9.8
    JWT: 1.2.5
    WP Cerber Security: 7.9

    my app ionic 3.9

    short story:
    the login, validate token: works fine.

    semi-code

    this.authenticationService.doLogin(value.username, value.password){
    — OK
    –get a valid token

    — /* call wp/v2/users/me */
    this.wordpressService.getUserMe(){
    — true section
    }error{
    — response wp/v2/users/me HTTP 401 Unauthorized
    }
    }

    the service always response HTTP 401 Unauthorized

    log
    https://drive.google.com/file/d/1Fadcw8J08hAYTJj9FRnWz8zY4hpLxyJ4/view

    “soluTion”
    after 2 days tracking the possible error, plugins, custom services etc
    if install the JWT version 1.2.4, the site do not respond HTTP 401 Unauthorized .

    thanks for some help

    I seem to have the same problem on my development machine – reverting to 1.2.4 fixed it

    Same here, in my case a fix for gutenberg in includes/class-jw-auth.php::define_public_hooks() (introduced in 1.2.5) messes up my authentication.

    i’m using the Rest-API from within an authenticated wordpress session, the added fix detects a logged in user and doesn’t call the determine_current_user filter. Because of this the token doesn’t get parsed and my ReST Controller reports there is no authenticated user.

    • This reply was modified 5 years, 11 months ago by egonvb.

    @goran87 I’ve spent about a week trying to debug this and was so confused bc I was also testing in Postman, which works with the Bearer {{token}} and stuff. Rollback to JWT v1.2.4 for now.

    I am trying to access thru Angular 6. I am getting Unauthorised error. To try with Jwt 1-2-4 I am not able to get 1.2.4 version. Can some one help me by sending that version.

    My mail id is [email protected]

    Thanking you in advance.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Plugin version 1.2.5 not authenticating users’ is closed to new replies.