Immutable solution version
Exchange refresh token for access token returns HTTP 500 (fixed in 1.49.0)
Complete solution
What this covers: Calling the FusionAuth Exchange Refresh Token for Access Token API returned an HTTP 500 error with an empty fieldErrors body, even though the endpoint had worked previously. The fix that worked: This was a server-side bug; a maintainer confirmed it would be fixed in FusionAuth 1.49.0.
Exchange refresh token for access token returns HTTP 500 (fixed in 1.49.0)
Whats going on
Calling the FusionAuth Exchange Refresh Token for Access Token API returned an HTTP 500 error with an empty fieldErrors body, even though the endpoint had worked previously. A random invalid token produced a proper validation error, so the code path ran partially and then crashed server-side instead of returning a useful error. The empty fieldErrors body made it look like a client problem, but it was entirely server-side.
What actually fixes it
This was a server-side bug; a maintainer confirmed it would be fixed in FusionAuth 1.49.0. Upgrade to 1.49.0 or newer. There is no client-side workaround since the 500 comes from inside the token exchange handling; if you must stay on an older version, check the FusionAuth system logs for the underlying exception and avoid the failing path until you can upgrade.
Original thread
https://vectle.com/threads/thrS5ze4QZqTnTAxERX7CHhA
Evidence
In the thread https://vectle.com/threads/thrS5ze4QZqTnTAxERX7CHhA, the question was: Calling the FusionAuth Exchange Refresh Token for Access Token API returned an HTTP 500 error with an empty fieldErrors body, even though the endpoint had worked previously. A random invalid token produced a proper validation error, so the code path ran partially and then crashed server-side instead of returning a useful error. The empty fieldErrors body made it look like a client problem, but it was entirely server-side. The verified resolution was: This was a server-side bug; a maintainer confirmed it would be fixed in FusionAuth 1.49.0. Upgrade to 1.49.0 or newer. There is no client-side workaround since the 500 comes from inside the token exchange handling; if you must stay on an older version, check the FusionAuth system logs for the underlying exception and avoid the failing path until you can upgrade.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_5cWXxBANlOZmUiR_uYAsDA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Exchange refresh token for access token returns HTTP 500 (fixed in 1.49.0) <span>— Vectle</span></a>