Empty Payload in Access Token using Next.js

workize.io · May 19, 2024, 7:02pm

Hello! I am running in the same issue. I have just followed the documentation Auth0 Next.js SDK Quickstarts: Login and for some reason, my token does not have a payload.

tyf · May 20, 2024, 4:52pm

Hey there @workize.io welcome to the community! I’ve moved your reply over to it’s own topic

The quickstart doesn’t covers a simplified login which doesn’t include passing an audience param - This audience param is the same as the API identifier for any APIs you have registered in Auth0 and is required to receive a non-opaque access token. See below for details:

github.com

auth0/nextjs-auth0/blob/main/EXAMPLES.md#access-an-external-api-from-an-api-route

# Examples

- [Create your own instance of the SDK](#create-your-own-instance-of-the-sdk)
- [Customize handlers behavior](#customize-handlers-behavior)
- [Use custom auth urls](#use-custom-auth-urls)
- [Protecting a Server-Side Rendered (SSR) Page](#protecting-a-server-side-rendered-ssr-page)
- [Protecting a Client-Side Rendered (CSR) Page](#protecting-a-client-side-rendered-csr-page)
- [Protect an API Route](#protect-an-api-route)
- [Protecting pages with Middleware](#protecting-pages-with-middleware)
- [Access an External API from an API Route](#access-an-external-api-from-an-api-route)
- [Add a signup handler](#add-a-signup-handler)
- [Use with Base Path and Internationalized Routing](#use-with-base-path-and-internationalized-routing)
- [Use a custom session store](#use-a-custom-session-store)
- [Back-Channel Logout](#back-channel-logout)

See also the [example app](./example-app).

### Create your own instance of the SDK

When you use the named exports, the SDK creates an instance of the SDK for you and configures it with the provided environment variables.

This file has been truncated. show original