token_expires field missing from jwt

  • Resolved danceshout

    (@danceshout)


    3 years, 3 months ago

    Currently running AAM 6.8.5 as updating beyond this version breaks functionality we need.

We use AAM to facilitate logins on an iOS app, but beyond AAM 6.8.5 we're unable to sign in. 

When I POST https://highfitness.com/wp-json/aam/v2/authenticate I get a response like:

{

    "user": {

        "data": {

            "ID": 4629,

            "user_login": "username",

            "user_nicename": "username",

            "display_name": "User Name",

            "user_url": "https://username.com/",

            "user_email": "[email protected]",

            "user_registered": "2020-09-18 02:17:00"

        }

    },

    "redirect": null,

    "jwt": {

        "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE2NzcxMzU3ODEsImlzcyI6Imh0dHBzOi8vaGlnaGZpdG5lc3MuY29tIiwiZXhwIjoxNjc3MjIyMTgxLCJqdGkiOiJhZWZkNDQ1MS02ZTgwLTQ5MGMtOWRkZC01ZWJlZTljYjE0ZDQiLCJ1c2VySWQiOjQ2MjksInJldm9jYWJsZSI6dHJ1ZSwicmVmcmVzaGFibGUiOm51bGx9._zZG2Y-YtuGwMyMDeLqfuSR-FsLqzBuwOadb2RY5i1E"

    }

}

It is missing the token_expires field in jwt. The app requires this to be present, so when it isn't it fails to parse the response.
Viewing 1 replies (of 1 total)
  • Plugin Author AAM Plugin

    (@vasyltech)

    3 years, 3 months ago

    Hello @danceshout,

    Thank you for the feedback. We’ll fix this in the upcoming release and document the changes here https://aamportal.com/advanced/restful/reference/jwt.

    Note, we are aggressively moving AAM to be API-first solution, so the new version of JWT RESTful API will be introduced shortly under /aam/v3/jwt namespace. I do not think we’ve done good job thinking through JWT API schemas in the past.

    Regards,

Viewing 1 replies (of 1 total)

The topic ‘token_expires field missing from jwt’ is closed to new replies.