• Home
  • Categories
  • Recent
  • Popular
  • Pricing
  • Contact us
  • Docs
  • Login
FusionAuth
  • Home
  • Categories
  • Recent
  • Popular
  • Pricing
  • Contact us
  • Docs
  • Login

JWT Refresh Returning 400

Scheduled Pinned Locked Moved Unsolved
Q&A
2
2
360
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M
    matt 3
    last edited by 17 Dec 2024, 11:01

    Hi I'm struggling to find an answer to a random (or seemingly random) issue.

    Every now and again when our application tries to get a new token from the /api/jwt/refresh endpoint it is returning 400. The refresh token lifetime is set for 43200 mins, JWT lifetime is 300 seconds.

    I can't seem to find a forced situation that I can replicate this. Have tried

    • Getting a token, waiting a couple of days and then refreshing
    • Getting token from one computer, then getting a new token from another and then refreshing from the first.
    • Mixing the above two things

    The one example I'm looking at in our dev env the token is for a user that hasn't been disabled etc in any way, the JWT had expire c2hrs before hand.

    Any advice on how to debug this or a potential solution would be amazing

    M 1 Reply Last reply 20 Dec 2024, 18:40 Reply Quote 0
    • M
      mark.robustelli @matt 3
      last edited by 20 Dec 2024, 18:40

      @matt-3 Have you enabled logging in FusionAuth? I would start there to see if there is anything happening internally that is causing the 400 response.

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post