Install Auth SDK
Learn how to configure the Wristband SDK for your Next.js application.
Installation
Install the Wristband Auth SDK using your preferred package manager CLI:
npm install @wristband/nextjs-authyarn add @wristband/nextjs-authpnpm add @wristband/nextjs-authConfiguration
Prerequisites
Before you can configure the SDK, you'll need to make sure you have the following values:
- WRISTBAND_APPLICATION_VANITY_DOMAIN
- WRISTBAND_CLIENT_ID
- WRISTBAND_CLIENT_SECRET
If you went through the Set Up a Wristband Application guide, you should have been presented with these three values after the application was provisioned. If you don't have the above values on hand, you can retrieve them from the Wristband dashboard by following the steps in this guide.
Configuring the SDK
Create an instance of WristbandAuth in the source root directory of your Next.js project (e.g.src/wristband.ts). Update the configuration properties with the values for your application.
Disabling Secure Cookies in Local DevelopmentBy default, WristbandAuth creates secure cookies (for tracking login state), meaning they are only sent over HTTPS connections. Most browsers make an exception for localhost and allow secure cookies to be sent over HTTP (e.g., http://localhost). However, some browsers, such as Safari, enforce stricter rules and never send secure cookies over HTTP, even for localhost.
If you need to disable the secure cookies for local development, set
dangerouslyDisableSecureCookies: truein the config properties. However, be sure to re-enable secure cookies before deploying to production.
// src/wristband.ts
import { createWristbandAuth } from '@wristband/nextjs-auth';
export const wristbandAuth = createWristbandAuth({
clientId: '<WRISTBAND_CLIENT_ID>',
clientSecret: '<WRISTBAND_CLIENT_SECRET>',
wristbandApplicationVanityDomain: '<WRISTBAND_APPLICATION_VANITY_DOMAIN>',
});// src/wristband.ts
import { createWristbandAuth } from '@wristband/nextjs-auth';
export const wristbandAuth = createWristbandAuth({
clientId: '<WRISTBAND_CLIENT_ID>',
clientSecret: '<WRISTBAND_CLIENT_SECRET>',
wristbandApplicationVanityDomain: '<WRISTBAND_APPLICATION_VANITY_DOMAIN>',
dangerouslyDisableSecureCookies: true,
});Updated about 10 hours ago
Next, we'll add a helper function to access user session data in your API routes and server-side rendering (SSR) functions.