Token Refresh with NextJS-Auth0 SDK

Knowledge Articles
, ,
1

Last Updated: Aug2, 2024

Overview

This article discusses the issues with configuring token refresh when utilizing Nextis-auth0 SDK with the Next-URQL client within production. It provides information on how mergeExchanges in URQL and client/server (middleware) token refreshes within NextJS should be configured

Applies To

  • NextJS-Auth0 SDK
  • Token Refresh

Solution

On the backend side, the Next.js implementation uses methods such as getAccessToken(). This will not work as the /authorize request is designed for use in an IFRAME for Silent Authentication or a POST to the /oauth/token endpoint if a Refresh Token is present. This is not possible in a backend application.

To use Refresh Tokens in our Next.js SDK, do the following:

  • Include the offline_access scope in the configuration (or AUTH0_SCOPE).
  • Check “Allow Offline Access” in the API Settings.
  • Make sure the “Refresh Token” grant is enabled in the Application Settings (this is the default).
2 Likes