Has /token json response changed?

  • Resolved dfaltermier

    (@dfaltermier)


    1 year, 11 months ago

    Hello support folks,

    I noticed that since upgrading the JWT Authentication for WP-API plugin from v1.2.6 to v1.3.2, the REACT frontend to our website is not getting the /wp-json/jwt-auth/v1/token json response content from our headless WP backend that it needs to authenticate a login attempt.

    The JWT Authentication for WP-API plugin, version 1.2.6, returns this working/complete json response:

    {
    "token": "eyJ0eXAiOiJ...",
    "user_clientID: false,
    "user_display_name: "cgadmin",
    "user_email": "[email protected]",
    "user_isAdmin: true,
    "user_nicename": "cgadmin",
    "user_roles: ["administrator"]
}

    The JWT Authentication for WP-API plugin, version 1.3.2, returns this non-working/incomplete json response:

    {
    "token": "eyJ0eXAiOiJ...",
    "user_email": "[email protected]",
    "user_nicename": "cgadmin",
    "user_display_name": "cgadmin"
}

    Has a change been made to the plugin that would remove these json values? Please advise on what I need to know in order to return these values again in the json response.

    WordPress Environment
    WP: v6.1.1
    PHP: v7.4

    Thanks!

    • This topic was modified 1 year, 11 months ago by dfaltermier.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Thread Starter dfaltermier

    (@dfaltermier)

    It turns out that someone on my team had made code changes to the 1.2.6 version of the plugin that was installed on the site. …sigh. Of course, updating the plugin overwrote that code. This problem has been identified and fixed. Nothing to do with this plugin at all. Disregard.

Viewing 1 replies (of 1 total)
  • The topic ‘Has /token json response changed?’ is closed to new replies.