chore: rename docs-nextra to docs

.eslintignore

@@ -23,10 +23,14 @@ pnpm-lock.yaml
 
 .docusaurus
 build
-docs/docs/reference/core
-docs/docs/reference/sveltekit
+docs/pages/reference/core
+docs/pages/reference/sveltekit
+docs/pages/reference/adapter
 static
 
+#  TODO: Enable
+docs-nextra
+
 # --------------- Packages ---------------
 
 coverage

.eslintrc.js

@@ -34,11 +34,11 @@ module.exports = {
       extends: ["plugin:jest/recommended"],
       env: { jest: true },
     },
-    {
-      files: ["docs/**"],
-      plugins: ["@docusaurus"],
-      extends: ["plugin:@docusaurus/recommended"],
-    },
+    // {
+    //   files: ["docs/**"],
+    //   plugins: ["@docusaurus"],
+    //   extends: ["plugin:@docusaurus/recommended"],
+    // },
     {
       // TODO: Expand to all packages
       files: ["packages/{core,sveltekit}/*.ts"],

.github/pr-labeler.yml

@@ -2,7 +2,7 @@
 adapters: ["packages/core/src/adapters.ts", "packages/adapter-*/**/*"]
 core: ["packages/core/src/**/*"]
 dgraph: ["packages/adapter-dgraph/**/*"]
-documentation: ["packages/docs/docs/**/*"]
+documentation: ["packages/docs/pages/**/*"]
 dynamodb: ["packages/adapter-dynamodb/**/*"]
 examples: ["apps/examples/**/*"]
 fauna: ["packages/adapter-fauna/**/*"]

.gitignore

@@ -82,8 +82,7 @@ packages/core/src/providers/oauth-types.ts
 packages/core/lib
 packages/core/providers
 packages/core/src/lib/pages/styles.ts
-docs/docs/reference/core
-docs/docs/reference/sveltekit
+docs/pages/reference/core
 
 
 # SvelteKit
@@ -93,7 +92,8 @@ packages/frameworks-sveltekit/.svelte-kit
 packages/frameworks-sveltekit/package
 packages/frameworks-sveltekit/vite.config.js.timestamp-*
 packages/frameworks-sveltekit/vite.config.ts.timestamp-*
+docs/pages/reference/sveltekit
 
 # Adapters
 
-docs/docs/reference/adapter
+docs/pages/reference/adapter

.prettierignore

@@ -13,16 +13,14 @@ pnpm-lock.yaml
 *.d.ts.map
 
 .svelte-kit
-.next
 .nuxt
 
 # --------------- Docs ---------------
 
-.docusaurus
-build
-docs/docs/reference/core
-docs/docs/reference/sveltekit
-static
+.next
+docs/pages/reference/core
+docs/pages/reference/sveltekit
+docs/pages/reference/adapter
 docs/providers.json
 
 # --------------- Packages ---------------

docs/.eslintrc

@@ -0,0 +1,3 @@
+{
+  "extends": "next/core-web-vitals"
+}

docs/README.md

@@ -1,66 +0,0 @@
-<p align="center">
-   <br/>
-   <a href="https://authjs.dev" target="_blank"><img width="150px" src="https://authjs.dev/img/logo/logo-sm.png" /></a>
-   <h3 align="center">Auth.js</h3>
-   <p align="center">Authentication for Next.js</p>
-   <p align="center">
-   Open Source. Full Stack. Own Your Data.
-   </p>
-   <p align="center" style="align: center;">
-      <a href="https://github.com/nextauthjs/next-auth/actions/workflows/release.yml?query=workflow%3ARelease">
-        <img src="https://github.com/nextauthjs/next-auth/actions/workflows/release.yml/badge.svg" alt="Release" />
-      </a>
-      <a href="https://packagephobia.com/result?p=@auth/core">
-        <img src="https://packagephobia.com/badge?p=@auth/core" alt="Bundle Size"/>
-      </a>
-      <a href="https://www.npmtrends.com/@auth/core">
-        <img src="https://img.shields.io/npm/dm/@auth/core" alt="Downloads" />
-      </a>
-      <a href="https://github.com/nextauthjs/next-auth/stargazers">
-        <img src="https://img.shields.io/github/stars/nextauthjs/next-auth" alt="Github Stars" />
-      </a>
-      <a href="https://www.npmjs.com/package/@auth/core">
-        <img src="https://img.shields.io/github/v/release/nextauthjs/next-auth?label=latest" alt="Github Stable Release" />
-      </a>
-   </p>
-</p>
-
-## Overview
-
-This is the repository for the documentation page for Auth.js!
-
-NextAuth.js is a complete open source authentication solution for [Next.js](http://nextjs.org/) applications.
-
-This documentation site is based on the [Docusaurus](https://docusaurus.io) framework.
-
-## Getting Started
-
-To start a local environment of this project, please do the following.
-
-1. Clone the repository.
-
-```bash
-$ git clone https://github.com/nextauthjs/docs.git
-```
-
-2. Install dependencies
-
-```bash
-$ npm install
-```
-
-3. Start the development server
-
-```bash
-$ npm start
-```
-
-And thats all! Now you should have a local copy of this docs site running at [localhost:3000](http://localhost:3000)!
-
-## Contributing
-
-We're open to all community contributions! If you'd like to contribute in any way, please first read our [Contributing Guide](https://github.com/nextauthjs/.github/blob/main/CONTRIBUTING.md).
-
-## License
-
-ISC

docs/assets/img/blobs/blob1.svg

@@ -0,0 +1,19 @@
+<!-- <svg width="1077" height="990" viewBox="0 0 1077 990" fill="none" xmlns="http://www.w3.org/2000/svg"> -->
+<!-- <path d="M909.079 176.687C486.468 1429.32 94.8519 797.145 -245.666 989.191L-273.518 122.311C-98.0847 109.104 255.784 81.3405 267.79 75.9479C282.798 69.2072 1153.31 -485.661 1071.51 -140.889C1022.28 -26.4819 1001.45 -97.0987 909.079 176.687Z" fill="url(#paint0_linear_228_76)" fill-opacity="1" /> -->
+<!-- <defs> -->
+<!-- <linearGradient id="paint0_linear_228_76" x1="588.47" y1="791.265" x2="238.137" y2="497.91" gradientUnits="userSpaceOnUse"> -->
+<!-- <stop stop-color="#FF4400"/> -->
+<!-- <stop offset="1" stop-color="#111" /> -->
+<!-- </linearGradient> -->
+<!-- </defs> -->
+<!-- </svg> -->
+<svg width="1056" height="855" viewBox="0 0 1056 855" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M888.078 42.3027C465.467 1294.94 73.851 662.761 -266.667 854.807L-294.519 -12.0732C-119.086 -25.2807 234.783 -53.0438 246.789 -58.4364C261.797 -65.1771 1132.31 -620.045 1050.51 -275.273C1001.28 -160.866 980.447 -231.483 888.078 42.3027Z" fill="url(#paint0_radial_228_76)"/>
+<defs>
+<radialGradient id="paint0_radial_228_76" cx="0" cy="0" r="1" gradientUnits="userSpaceOnUse" gradientTransform="translate(666.999 571.116) rotate(-129.513) scale(513.947 862.777)">
+<stop stop-color="#FF4400"/>
+<stop offset="1" stop-color="#111111"/>
+</radialGradient>
+</defs>
+</svg>
+

docs/assets/img/blobs/blob2.svg

@@ -0,0 +1,20 @@
+<!-- <svg width="1405" height="1025" viewBox="0 0 1405 1025" fill="none" xmlns="http://www.w3.org/2000/svg"> -->
+<!-- <path d="M1180.05 977.4C483.802 708.04 103.247 143.506 0 -105.091L1102.61 -196C1418.53 307.367 1876.29 1246.76 1180.05 977.4Z" fill="url(#paint0_linear_228_83)" fill-opacity="0.44"/> -->
+<!-- <defs> -->
+<!-- <linearGradient id="paint0_linear_228_83" x1="185.171" y1="460.565" x2="641.405" y2="-62.9701" gradientUnits="userSpaceOnUse"> -->
+<!-- <stop stop-color="#BB44CC"/> -->
+<!-- <stop offset="1" stop-color="#BB44CC" stop-opacity="0"/> -->
+<!-- </linearGradient> -->
+<!-- </defs> -->
+<!-- </svg> -->
+
+<svg width="1405" height="1025" viewBox="0 0 1405 1025" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M1180.05 977.4C483.802 708.04 103.247 143.506 0 -105.091L1102.61 -196C1418.53 307.367 1876.29 1246.76 1180.05 977.4Z" fill="url(#paint0_radial_228_83)"/>
+<defs>
+<radialGradient id="paint0_radial_228_83" cx="0" cy="0" r="1" gradientUnits="userSpaceOnUse" gradientTransform="translate(498 619) rotate(-46.5881) scale(548.572 1194.34)">
+<stop stop-color="#BB44CC"/>
+<stop offset="1" stop-color="#111111"/>
+</radialGradient>
+</defs>
+</svg>
+

docs/assets/img/blobs/blob3.svg

@@ -0,0 +1,20 @@
+<!-- <svg width="2402" height="275" viewBox="0 0 2402 275" fill="none" xmlns="http://www.w3.org/2000/svg"> -->
+<!-- <path d="M305.668 155.376C1150.52 -387.169 3270.85 708.01 2011.14 262.274L1847.48 804.627C1613.84 721.267 1142.31 553.804 1125.29 550.832C1104 547.117 -168.361 431.431 18.8067 264.119C109.949 220.108 121.011 273.958 305.668 155.376Z" fill="url(#paint0_linear_228_78)" fill-opacity="0.66"/> -->
+<!-- <defs> -->
+<!-- <linearGradient id="paint0_linear_228_78" x1="869.047" y1="-51.7999" x2="921.583" y2="353.448" gradientUnits="userSpaceOnUse"> -->
+<!-- <stop stop-color="#44BBCC"/> -->
+<!-- <stop offset="1" stop-color="#44BBCC" stop-opacity="0.12"/> -->
+<!-- </linearGradient> -->
+<!-- </defs> -->
+<!-- </svg> -->
+
+<svg width="2402" height="275" viewBox="0 0 2402 275" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M305.668 155.376C1150.52 -387.169 3270.85 708.01 2011.14 262.274L1847.48 804.627C1613.84 721.267 1142.31 553.804 1125.29 550.832C1104 547.117 -168.361 431.431 18.8067 264.119C109.949 220.108 121.011 273.958 305.668 155.376Z" fill="url(#paint0_radial_228_78)"/>
+<defs>
+<radialGradient id="paint0_radial_228_78" cx="0" cy="0" r="1" gradientUnits="userSpaceOnUse" gradientTransform="translate(883.5 -66) rotate(93.0267) scale(757.557 879.417)">
+<stop stop-color="#44BBCC"/>
+<stop offset="1" stop-color="#111111"/>
+</radialGradient>
+</defs>
+</svg>
+

docs/components/marquee.jsx

@@ -0,0 +1,66 @@
+import { useState, useEffect } from "react"
+import { motion } from "framer-motion"
+
+const clamp = (num, min, max) => Math.min(Math.max(num, min), max)
+
+export default function Marquee({ files }) {
+  const [{ width, height }, setSize] = useState({ height: 0, width: 0 })
+  useEffect(() => {
+    setSize({
+      width: window.innerWidth,
+      height: window.innerHeight,
+    })
+  }, [])
+
+  if (width === 0) return
+
+  return (
+    <div className="absolute w-full h-full top-0 left-0 dark:opacity-5 opacity-20 saturate-0 brightness-75 dark:brightness-[1000] -z-20 overflow-hidden flex flex-col marquee-wrapper">
+      {files.map((name) => (
+        <MarqueeItem key={name} name={name} width={width} height={height} />
+      ))}
+    </div>
+  )
+}
+
+function MarqueeItem({ name, width, height }) {
+  const [y] = useState(height * Math.random())
+  const [reset, setReset] = useState(false)
+  const [duration] = useState(clamp(Math.random() * 25, 20, 25))
+  const offset = Math.random() * width
+  useEffect(() => {
+    const timeout =
+      setTimeout(() => {
+        setReset(true)
+      }, (1000 * (width - offset)) / duration) - 2000
+    return () => clearTimeout(timeout)
+  }, [duration, width, offset])
+  return (
+    <motion.span
+      key={name + reset}
+      className="absolute flex items-center justify-center"
+      initial={{ x: reset ? 0 : offset, y }}
+      animate={{ x: width }}
+      transition={{
+        repeat: Infinity,
+        duration: reset ? duration : (width - offset) / duration,
+        ease: "linear",
+      }}
+    >
+      <motion.img
+        src={`/img/providers/${name}`}
+        alt={name}
+        className="relative w-12 drop-shadow-xl"
+        initial={{ opacity: 0, scale: 0.5 }}
+        animate={{ opacity: 1, scale: 1 }}
+        transition={{
+          delay: reset ? 0 : Math.random() * 5,
+          duration: 1,
+          type: "spring",
+
+          stiffness: 150,
+        }}
+      />
+    </motion.span>
+  )
+}

docs/components/triangle.jsx

@@ -0,0 +1,85 @@
+export default function Triangle({ className }) {
+  return (
+    <svg
+      id="triangle"
+      viewBox="0 0 445 379"
+      className={className}
+      fill="none"
+      xmlns="http://www.w3.org/2000/svg"
+    >
+      <style jsx>
+        {`
+          @media (prefers-color-scheme: light) {
+            #triangle-0 {
+              fill: #000;
+            }
+            #triangle-1 {
+              fill: #ff4400;
+            }
+            #triangle-2 {
+              fill: #bb44cc;
+            }
+            #triangle-3 {
+              fill: #44bbcc;
+            }
+          }
+        `}
+      </style>
+      <path
+        id="triangle-0"
+        d="M334.033 238.33L222.692 46.7201L111.352 238.33H334.033Z"
+        fill="#fff"
+      />
+      <path
+        id="triangle-1"
+        d="M198.174 1.12812L4.62255 51.2473C1.37638 52.0878 -0.550786 55.4258 0.344333 58.6574L53.7157 251.338C55.1362 256.466 62.0336 257.344 64.6942 252.736L204.874 9.93656C207.535 5.32834 203.325 -0.205751 198.174 1.12812Z"
+        fill="url(#triangle-1-gradient)"
+      />
+      <path
+        id="triangle-2"
+        d="M246.294 1.12825L439.846 51.2473C443.092 52.0879 445.019 55.4259 444.124 58.6574L390.753 251.338C389.332 256.466 382.435 257.344 379.774 252.736L239.594 9.93665C236.933 5.32844 241.143 -0.205634 246.294 1.12825Z"
+        fill="url(#triangle-2-gradient)"
+      />
+      <path
+        id="triangle-3"
+        d="M361.388 286.577L225.585 377.959C223.559 379.322 220.91 379.322 218.885 377.959L83.0814 286.577C78.1672 283.27 80.5079 275.599 86.4311 275.599H358.039C363.962 275.599 366.303 283.27 361.388 286.577Z"
+        fill="url(#triangle-3-gradient)"
+      />
+      <defs>
+        <linearGradient
+          id="triangle-1-gradient"
+          x1="-1.28386"
+          y1="52.7769"
+          x2="134.785"
+          y2="131.336"
+          gradientUnits="userSpaceOnUse"
+        >
+          <stop stopColor="#992900" />
+          <stop offset="1" stopColor="#FF4400" />
+        </linearGradient>
+        <linearGradient
+          id="triangle-2-gradient"
+          x1="445.753"
+          y1="52.7769"
+          x2="309.684"
+          y2="131.336"
+          gradientUnits="userSpaceOnUse"
+        >
+          <stop stopColor="#6D2178" />
+          <stop offset="1" stopColor="#BB44CC" />
+        </linearGradient>
+        <linearGradient
+          id="triangle-3-gradient"
+          x1="222.236"
+          y1="380.213"
+          x2="222.236"
+          y2="275.599"
+          gradientUnits="userSpaceOnUse"
+        >
+          <stop stopColor="#1B5B64" />
+          <stop offset="1" stopColor="#44BBCC" />
+        </linearGradient>
+      </defs>
+    </svg>
+  )
+}

docs/docs/concepts/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Concepts",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/getting-started/01-introduction.md

@@ -1,44 +0,0 @@
----
-title: Introduction
-sidebar_position: 0
----
-
-## About Auth.js
-
-Auth.js is a complete open-source authentication solution for web applications. Check out the live demos of Auth.js in action:
-
-- [Next.js](https://next-auth-example.vercel.app/)
-- [SvelteKit](https://sveltekit-auth-example.vercel.app/)
-- [SolidStart](https://auth-solid.vercel.app/)
-
-Continue to our tutorials to see how to use Auth.js for authentication:
-
-- [Setup with OAuth](/getting-started/oauth-tutorial)
-- [Setup with magic links](/getting-started/email-tutorial)
-- [Integrating with external auth](/getting-started/credentials-tutorial)
-
-### Battery included
-
-- Built in support for 60+ popular services (Google, Facebook, Auth0, Apple…)
-- Built-in email/password-less/magic link
-- Use with any OAuth 2 or OpenID Connect provider
-- Use with any username/password store
-
-### Flexible
-- Runtime agnostic - run anywhere! Vercel Edge Functions, Node.js, Serverless, etc.
-- Use with any modern framework! Next.js, SolidStart, SvelteKit, etc.
-- [Bring Your Own Database](/getting-started/databases) - or none! MySQL, Postgres, MSSQL, MongoDB, etc. Choose database sessions or JWT.
-
-_Note: Email sign-in requires a database to store single-use verification tokens._
-
-### Secure by default
-- Signed, prefixed, server-only cookies
-- Built-in CSRF protection
-- Doesn't rely on client-side JavaScript
-- JWT with JWS / JWE / JWK.
-
-## Credits
-
-Auth.js is an open-source project that is only possible [thanks to contributors](/contributors).
-
-To financially support the development of Auth.js, you can check our [OpenCollective](https://opencollective.com/nextauth) page. We appreciate your support 💚.

docs/docs/getting-started/02-oauth-tutorial.mdx

@@ -1,369 +0,0 @@
----
-title: OAuth authentication
----
-
-import creatingOauthAppImg from "./img/getting-started-creating-oauth-app.png"
-import addingCallbackUrlImg from "./img/getting-started-oauth-callback-url.png"
-import gettingClientIdSecretImg from "./img/getting-started-oauth-clientid-secret.png"
-import startAppAndSignInImg from "./img/getting-started-app-start.png"
-import githubAuthCredentials from "./img/getting-started-github-auth.png"
-import nextAuthUserLoggedIn from "./img/getting-started-nextauth-success.png"
-import Tabs from "@theme/Tabs"
-import TabItem from "@theme/TabItem"
-
-The goal of Auth.js is that you can add authentication easily to your project with just a few lines of code.
-
-The fastest way to set up Auth.js is with an [OAuth](/concepts/oauth) provider. In this tutorial, we'll be setting Auth.js in a web application to be able to log in with **GitHub**.
-
-:::info
-Auth.js comes with a list of [built-in providers](/reference/providers/oauth-builtin) (Google, Facebook, Twitter, etc.). You can also integrate it with your OAuth service by [building a custom provider](/guides/providers/custom-provider).
-:::
-
-## 1. Configuring Auth.js
-
-To add Auth.js to your project:
-
-<Tabs groupId="frameworks" queryString>
-  <TabItem value="next" label="Next.js" default>
-
-### Prerequisites
-
-This tutorial assumes you have a Next.js application set up. If you don't, you can follow the [Next.js tutorial](https://nextjs.org/learn/basics/create-nextjs-app) to get started.
-
-### Installing NextAuth.js
-
-```bash npm2yarn
-npm install next-auth
-```
-
-:::info
-We are working on a new `@auth/nextjs` package that will make it easier to set up Auth.js with Next.js. Stay tuned! For now, you can use the `next-auth` package.
-:::
-
-### Creating the server config
-
-Create the following [API route](https://nextjs.org/docs/api-routes/dynamic-api-routes#catch-all-api-routes) file. This route contains the necessary configuration for NextAuth.js, as well as the dynamic route handler:
-
-```ts title="pages/api/auth/[...nextauth].ts"
-import NextAuth from "next-auth"
-import GithubProvider from "next-auth/providers/github"
-
-export default NextAuth({
-  providers: [
-    GithubProvider({
-      clientId: process.env.GITHUB_ID,
-      clientSecret: process.env.GITHUB_SECRET,
-    }),
-  ],
-})
-```
-
-:::info
-
-Behind the scenes, this creates all the relevant OAuth API routes within `/api/auth/*` so that auth API requests to:
-
-- [GET `/api/auth/signin`](https://authjs.dev/reference/rest-api#get--apiauthsignin)
-- [POST `/api/auth/signin/:provider`](https://authjs.dev/reference/rest-api#post--apiauthsigninprovider)
-- [GET/POST `/api/auth/callback/:provider`](https://authjs.dev/reference/rest-api#get--post--apiauthcallbackprovider)
-- [GET `/api/auth/signout`](https://authjs.dev/reference/rest-api#get--apiauthsignout)
-- [POST `/api/auth/signout`](https://authjs.dev/reference/rest-api#post--apiauthsignout)
-- [GET `/api/auth/session`](https://authjs.dev/reference/rest-api#get--apiauthsession)
-- [GET `/api/auth/csrf`](https://authjs.dev/reference/rest-api#get--apiauthcsrf)
-- [GET `/api/auth/providers`](https://authjs.dev/reference/rest-api#get--apiauthproviders)
-
-can be handled by NextAuth.js. In this way, NextAuth.js stays in charge of the whole application's authentication request/response flow.
-
-NextAuth.js is fully customizable - [our guides section](/guides/overview) teaches you how to set it up to handle auth in different ways. All the possible configuration options are [listed here](/reference/configuration/auth-config).
-:::
-
-### Adding environment variables
-
-You may notice we are using environment variables in the code example above. We take the value of `GITHUB_ID` and `GITHUB_SECRET` from the GitHub Developer OAuth Portal. See [Configuring OAuth Provider](/getting-started/oauth-tutorial#2-configuring-oauth-provider) section on how to get those.
-
-In your project root, create a `.env.local` file and add the `NEXTAUTH_SECRET` environment variable:
-
-```title=".env.local"
-NEXTAUTH_SECRET="This is an example"
-```
-
-`NEXTAUTH_SECRET` is a random string used by the library to encrypt tokens and email verification hashes, and **it's mandatory to keep things secure**! 🔥 🔐 . You can use:
-
-```
-$ openssl rand -base64 32
-```
-
-or https://generate-secret.vercel.app/32 to generate a random value for it.
-
-### Exposing the session via `SessionProvider`:
-
-NextAuth.js provides [`useSession()`](/reference/react/#usesession) - a [React Hooks](https://reactjs.org/docs/hooks-intro.html) to access the session data and status. To use it first you'll need to expose the session context - [`<SessionProvider />`](/reference/react/#sessionprovider) - at the top level of your application:
-
-```ts title="pages/_app.tsx"
-import { SessionProvider } from "next-auth/react"
-
-export default function App({
-  Component,
-  pageProps: { session, ...pageProps },
-}) {
-  return (
-    <SessionProvider session={session}>
-      <Component {...pageProps} />
-    </SessionProvider>
-  )
-}
-```
-
-Instances of `useSession` (more on it in the next section) will have access to the session data and status. The `<SessionProvider />` also keep the session updated and synced between browser tabs and windows. 💪🏽
-
-:::tip
-Check our [client docs](/reference/react/) to learn all the available options for handling sessions on the browser.
-:::
-
-### Consuming the session via hooks
-
-You can use the `useSession` hook from anywhere in your application (E.g. in a header component). Behind the scenes, the hook will connect to the `<SessionProvider />` to read the current user session. Learn more about React Context in the [React docs](https://reactjs.org/docs/context.html).
-
-```ts title="pages/overview.tsx"
-import { useSession, signIn, signOut } from "next-auth/react"
-
-export default function CamperVanPage() {
-  const { data: session, status } = useSession()
-  const userEmail = session?.user.email
-
-  if (status === "loading") {
-    return <p>Hang on there...</p>
-  }
-
-  if (status === "authenticated") {
-    return (
-      <>
-        <p>Signed in as {userEmail}</p>
-        <button onClick={() => signOut()}>Sign out</button>
-        <img src="https://cdn.pixabay.com/photo/2017/08/11/19/36/vw-2632486_1280.png" />
-      </>
-    )
-  }
-
-  return (
-    <>
-      <p>Not signed in.</p>
-      <button onClick={() => signIn("github")}>Sign in</button>
-    </>
-  )
-}
-```
-
-### Protecting API Routes
-
-To protect your API Routes (blocking unauthorized access to resources), you can use [`getServerSession()`](/reference/nextjs#getserversession) to know whether a session exists or not:
-
-```ts title="pages/api/movies/list.ts"
-import { getServerSession } from "next-auth/next"
-import { authOptions } from "../auth/[...nextauth]"
-
-export default async function listMovies(req, res) {
-  const session = await getServerSession(req, res, authOptions)
-
-  if (session) {
-    res.send({
-      movies: [
-        { title: "Alien vs Predator", id: 1 },
-        { title: "Reservoir Dogs", id: 2 },
-      ],
-    })
-  } else {
-    res.send({
-      error: "You must sign in to view movies.",
-    })
-  }
-}
-```
-
-  </TabItem>
-  <TabItem value="sveltekit" label="SvelteKit">
-TODO: SvelteKit
-  </TabItem>
-  <TabItem value="solidstart" label="SolidStart">
-TODO: SolidStart
-  </TabItem>
-  <TabItem value="core" label="Vanilla (No Framework)">
-TODO Core
-  </TabItem>
-</Tabs>
-
-## 2. Configuring OAuth Provider
-
-Ok, we have our app set up with NextAuth.js, however, if you run the app right now, it won't work as we haven't configured our OAuth provider (**GitHub**) yet.
-
-:::info
-When using OAuth you're asking for a third-party service (in this case GitHub, although it could be Google, Twitter, etc...) to handle user authentication for your app.
-:::
-
-We need to register our new app in GitHub, so that when NextAuth.js forwards the authorization requests to it, GitHub can recognize your application and prompt the user to sign in.
-
-<img src={creatingOauthAppImg} />
-
-Log in to **GitHub**, go to [`Settings / Developers / OAuth Apps`](https://github.com/settings/developers) and click "New OAuth App"
-
-Next, you'll be presented with a screen to add details about your new application. Fill in the required fields, but pay extra attention to the **Authorization Callback URL** one:
-
-<img src={addingCallbackUrlImg} />
-
-The callback URL we insert should have the following pattern:
-
-```
-[origin]/api/auth/callback/[provider]
-```
-
-In this case, given we want to try our authentication working locally on our machine and we're using **GitHub** as our OAuth provider, it'll be:
-
-<Tabs groupId="frameworks">
-  <TabItem value="next" label="Next.js" default>
-
-```
-http://localhost:3000/api/auth/callback/github
-```
-
-:::info
-NextAuth.js will already create this API endpoint for you when we start the application later. Note that because we're using Next.js, locally it starts our server on port `3000` by default. Hence, the origin is `http://localhost:3000`.
-:::
-
-  </TabItem>
-  <TabItem value="sveltekit" label="SvelteKit">
-
-```
-http://localhost:5173/auth/callback/github
-```
-
-  </TabItem>
-  <TabItem value="solidstart" label="SolidStart">
-    TODO SolidStart
-  </TabItem>
-  <TabItem value="core" label="Vanilla (No Framework)">
-TODO Core
-  </TabItem>
-</Tabs>
-:::info
-The last part of the URL, `[provider]`, is the ID of the provider you're using. In this case, we're using GitHub, so it's `github`. If you're using Google, it'll be `google`, etc... We keep track of the provider IDs internally.
-The same id is used in the `signIn()` method we saw earlier.
-:::
-To register, tap on "Register application" button.
-
-The next screen shows all the configurations for your newly created OAuth app. For now, we need two things from it - the **Client ID** and **Client Secret**:
-
-<img src={gettingClientIdSecretImg} />
-
-The Client ID is always there, a public identifier of your OAuth application within GitHub. Click on the **Generate a new client Secret** button and should be presented with a new string (which is just a randomized string).
-
-:::warning
-Keep both your Client ID and Client Secret secure and never expose them to the public or share them with people outside your organization. With them, a malicious actor could hijack your application and cause you and your user serious problems!
-:::
-
-Cool! We have finished configuring our OAuth provider, now let's wire all together so we can finally see authentication working in our app!
-
-:::info
-As noted previously, NextAuth.js has built-in support for multiple OAuth providers, <a href="">here is the full list</a>. You can also easily build your own in case the provider you need is not on the list.
-
-Note that, for each provider, the configuration process will be similar to what we just did:
-
-1. Log in to the provider
-2. Create create your OAuth application within it
-3. Set the callback URL
-4. Get the Client ID and Generate a Client Secret
-:::
-
-## 3. Wiring all together
-
-Finally, we just need to reference our **Client ID** and **Client Secret** we just generated in the previous in our Auth.js config. In this way, the library will be able to use them when forwarding users to GitHub, and GitHub will be able to recognize the request as generated from our application.
-
-Now let's copy both the Client ID and Client Secret and paste them into an environment file in the root of your project like so:
-
-```title=".env.local"
-GITHUB_ID=12345
-GITHUB_SECRET=67890
-```
-
-Here is our server configuration file again:
-
-<Tabs groupId="frameworks">
-  <TabItem value="next" label="Next.js" default>
-
-```ts title="pages/api/auth/[...nextauth].ts"
-import NextAuth from "next-auth"
-import GithubProvider from "next-auth/providers/github"
-
-export default NextAuth({
-  providers: [
-    GithubProvider({
-      clientId: process.env.GITHUB_ID,
-      clientSecret: process.env.GITHUB_SECRET,
-    }),
-  ],
-})
-```
-
-Great! We're now ready to run our application locally. Start the Next.js app by running on your terminal the following command and navigating to [`http://localhost:3000`](http://localhost:3000):
-
-```
-$ npm run next dev
-```
-
-  </TabItem>
-  <TabItem value="sveltekit" label="SvelteKit">
-TODO SvelteKit
-  </TabItem>
-  <TabItem value="solidstart" label="SolidStart">
-TODO SolidStart
-  </TabItem>
-  <TabItem value="core" label="Vanilla (No Framework)">
-TODO Core
-  </TabItem>
-</Tabs>
-
-You should see the following page:
-
-<img src={startAppAndSignInImg} />
-
-Click on "Sign in" and then on "Sign in with GitHub": Auth.js will redirect you to GitHub, and GitHub will recognize our app [that we just registered](#2-configuring-oauth-provider) and ask the user (in this case you) to enter its credentials to proceed:
-
-<img src={githubAuthCredentials} />
-
-Once inserted and correct, GitHub will redirect the user to our app and NextAuth.js will take care of any further calls with GitHub to get access to the user profile and start a user session safely in the background:
-
-<img src={nextAuthUserLoggedIn} />
-
-Great! We have completed the whole E2E authentication flow setup so that users can log in to our application through GitHub!
-
-## 4. Deploying to production
-
-### Configuring different environments
-
-It's normal to test your application in different environments. Usually, you'll have a development environment (when you run the application locally on your machine), a staging environment (for team members to try the application), and a production environment.
-
-For each environment, you need to create an OAuth application in your provider respectively, as [we did previously](#2-configuring-oauth-provider), and point the **callback URL** to it.
-
-For instance, in the previous section, we pointed the callback URL to `http://localhost:3000/api/auth/callback/github` as we wanted to test our application in the development environment.
-
-If we were to deploy our app to production, we would need to create a new **OAuth App** in GitHub (calling it something like "Van life – prod") and point the **callback URL** to our production domain: `https://example.com/api/auth/callback/github`
-
-Finally, we would need to point the environment variables we set ( `GITHUB_ID` and `GITHUB_SECRET` ) to the credentials of the OAuth app we want our application to run with.
-
-### Setting up `NEXTAUTH_URL`
-
-:::tip
-Skip this section if you are deploying to Vercel.
-:::
-
-When deploying your site, **you need to set** the `NEXTAUTH_URL` environment variable to the canonical URL of your website:
-
-```
-NEXTAUTH_URL=https://example.com
-```
-
-:::warning
-In production, this needs to be set as an environment variable on the service you use to deploy your app.
-
-To set environment variables on Vercel, you can use the [dashboard](https://vercel.com/dashboard) or the `vercel env pull` [command](https://vercel.com/docs/build-step#development-environment-variables).
-:::
-
-For more information please check out our [deployment page](/guides/basics/deployment).

docs/docs/getting-started/06-databases.md

@@ -1,18 +0,0 @@
----
-title: Databases
----
-
-Auth.js offers multiple database adapters. Check our guides on:
-
-- [using a database adapter](/guides/adapters/using-a-database-adapter)
-- [creating your own](/guides/adapters/creating-a-database-adapter)
-
-> As of **v4** Auth.js no longer ships with an adapter included by default. If you would like to persist any information, you need to install one of the many available adapters yourself. See the individual adapter documentation pages for more details.
-
-To learn more about databases in Auth.js and how they are used, check out [databases in the FAQ](/concepts/faq#databases).
-
----
-
-## How to use a database
-
-See the [documentation for adapters](/reference/adapters/overview) for more information on advanced configuration, including how to use Auth.js with other databases using a [custom adapter](/guides/adapters/creating-a-database-adapter).

docs/docs/getting-started/08-upgrade-to-v4.md

@@ -1,612 +0,0 @@
----
-title: Upgrade Guide (v4)
----
-
-Auth.js version 4 includes a few breaking changes from the last major version (3.x). So we're here to help you upgrade your applications as smoothly as possible. It should be possible to upgrade from any version of 3.x to the latest 4 release by following the next few migration steps.
-
-:::note
-Version 4 has been released to GA 🚨
-
-We encourage users to try it out and report any and all issues they come across.
-:::
-
-You can upgrade to the new version by running:
-
-```bash npm2yarn
-npm install next-auth
-```
-
-## `next-auth/jwt`
-
-We no longer have a default export in `next-auth/jwt`.
-To comply with this, change the following:
-
-```diff
-- import jwt from "next-auth/jwt"
-+ import { getToken } from "next-auth/jwt"
-```
-
-## `next-auth/react`
-
-We've renamed the client-side import source to `next-auth/react`. To comply with this change, you will simply have to rename anywhere you were using `next-auth/client`.
-
-For example:
-
-```diff
-- import { useSession } from "next-auth/client"
-+ import { useSession } from "next-auth/react"
-```
-
-We've also made the following changes to the names of the exports:
-
-- `setOptions`: Not exposed anymore, use [`SessionProvider` props](/reference/react/#sessionprovider)
-- `options`: Not exposed anymore, [use `SessionProvider` props](/reference/react/#sessionprovider)
-- `session`: Renamed to `getSession`
-- `providers`: Renamed to `getProviders`
-- `csrfToken`: Renamed to `getCsrfToken`
-- `signin`: Renamed to `signIn`
-- `signout`: Renamed to `signOut`
-- `Provider`: Renamed to `SessionProvider`
-
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.12
-
-## `SessionProvider`
-
-Version 4 makes using the `SessionProvider` mandatory. This means that you will have to wrap any part of your application using `useSession` in this provider, if you were not doing so already. The `SessionProvider` has also undergone a few further changes:
-
-- `Provider` is renamed to `SessionProvider`
-- The options prop is now flattened as the props of SessionProvider.
-- `keepAlive` has been renamed to `refetchInterval`.
-- `clientMaxAge` has been removed in favor of `refetchInterval`, as they overlap in functionality, with the difference that `refetchInterval` will keep re-fetching the session periodically in the background.
-
-The best practice for wrapping your app in Providers is to do so in your `pages/_app.jsx` file.
-
-An example use-case with these new changes:
-
-```jsx
-import { SessionProvider } from "next-auth/react"
-
-export default function App({
-  Component,
-  pageProps: { session, ...pageProps },
-}) {
-  return (
-    // `session` comes from `getServerSideProps` or `getInitialProps`.
-    // Avoids flickering/session loading on first load.
-    <SessionProvider session={session} refetchInterval={5 * 60}>
-      <Component {...pageProps} />
-    </SessionProvider>
-  )
-}
-```
-
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.12
-
-## Providers
-
-Providers now need to be imported individually.
-
-```diff
-- import Provider from "next-auth/providers"
-- Providers.Auth0({...})
-- Providers.Google({...})
-+ import Auth0Provider from "next-auth/providers/auth0"
-+ import GoogleProvider from "next-auth/providers/google"
-+ Auth0Provider({...})
-+ GoogleProvider({...})
-```
-
-1. The `AzureADB2C` provider has been renamed `AzureAD`.
-2. The `Basecamp` provider has been removed, see explanation [here](https://github.com/basecamp/api/blob/master/sections/authentication.md#on-authenticating-users-via-oauth).
-3. The GitHub provider by default now will not request full write access to user profiles. If you need this scope, please add `user` to the scope option manually.
-
-The following new options are available when defining your Providers in the configuration:
-
-1. `authorization` (replaces `authorizationUrl`, `authorizationParams`, `scope`)
-2. `token` replaces (`accessTokenUrl`, `headers`, `params`)
-3. `userinfo` (replaces `profileUrl`)
-4. `issuer`(replaces `domain`)
-
-For more details on their usage, please see [options](/reference/providers/oauth) section of the OAuth Provider documentation.
-
-When submitting a new OAuth provider to the repository, the `profile` callback is expected to only return these fields from now on: `id`, `name`, `email`, and `image`. If any of these are missing values, they should be set to `null`.
-
-Also worth noting is that `id` is expected to be returned as a `string` type (For example if your provider returns it as a number, you can cast it by using the `.toString()` method). This makes the returned profile object comply across all providers/accounts/adapters, and hopefully cause less confusion in the future.
-
-Implemented in: https://github.com/nextauthjs/next-auth/pull/2411
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.20
-
-## `useSession` Hook
-
-The `useSession` hook has been updated to return an object. This allows you to test states much more cleanly with the new `status` option.
-
-```diff
-- const [ session, loading ] = useSession()
-+ const { data: session, status } = useSession()
-+ const loading = status === "loading"
-```
-
-[Check the docs](/reference/react/#usesession) for the possible values of both `session.status` and `session.data`.
-
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.18
-
-## Named Parameters
-
-We have changed the arguments to our callbacks to the named parameters pattern. This way you don't have to use dummy `_` placeholders or other tricks.
-
-### Callbacks
-
-The signatures for the callback methods now look like this:
-
-```diff
-- signIn(user, account, profileOrEmailOrCredentials)
-+ signIn({ user, account, profile, email, credentials })
-```
-
-```diff
-- redirect(url, baseUrl)
-+ redirect({ url, baseUrl })
-```
-
-```diff
-- session(session, tokenOrUser)
-+ session({ session, token, user })
-```
-
-```diff
-- jwt(token, user, account, OAuthProfile, isNewUser)
-+ jwt({ token, user, account, profile, isNewUser })
-```
-
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.17
-
-### Events
-
-Two event signatures have changed to also use the named parameters pattern, `signOut` and `updateUser`.
-
-```diff
-// [...nextauth].js
-...
-events: {
-- signOut(tokenOrSession),
-+ signOut({ token, session }), // token if using JWT, session if DB persisted sessions.
-- updateUser(user)
-+ updateUser({ user })
-}
-```
-
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.20
-
-## JWT configuration
-
-We have removed some of the [configuration options](/reference/configuration/auth-config) when using JSON Web Tokens, [here's the PR](https://github.com/nextauthjs/next-auth/pull/3039) for more context.
-
-```diff
-export default NextAuth({
-  // ...
-  jwt: {
-    secret,
-    maxAge,
--   encryptionKey
--   signingKey
--   encryptionKey
--   verificationOptions
-    encode({
-        token
-        secret
-        maxAge
--       signingKey
--       signingOptions
--       encryptionKey
--       encryptionOptions
--       encryption
-    }) {},
-    decode({
-        token
-        secret
--       maxAge
--       signingKey
--       verificationKey
--       verificationOptions
--       encryptionKey
--       decryptionKey
--       decryptionOptions
--       encryption
-    }) {}
-  }
-})
-```
-
-## Logger API
-
-The logger API has been simplified to use at most two parameters, where the second is usually an object (`metadata`) containing an `error` object. If you are not using the logger settings you can ignore this change.
-
-```diff
-// [...Auth.js]
-import log from "some-logger-service"
-...
-logger: {
-- error(code, ...message) {},
-+ error(code, metadata) {},
-- warn(code, ...message) {},
-+ warn(code) {}
-- debug(code, ...message) {}
-+ debug(code, metadata) {}
-}
-```
-
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.19
-
-## `nodemailer`
-
-Like `typeorm` and `prisma`, [`nodemailer`](https://npmjs.com/package/nodemailer) is no longer included as a dependency by default. If you are using the Email provider you must install it in your project manually, or use any other Email library in the [`sendVerificationRequest`](/reference/providers/email) callback. This reduces bundle size for those not actually using the Email provider. Remember, when using the Email provider, it is mandatory to also use a database adapter due to the fact that verification tokens need to be persisted longer term for the magic link functionality to work.
-
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.2
-
-## Theme
-
-We have added some basic customization options to our built-in pages like `signin`, `signout`, etc.
-
-These can be set under the `theme` configuration key. This used to be a string which only controlled the color scheme option. Now it is an object with the following options:
-
-```js
-theme: {
-  colorScheme: "auto", // "auto" | "dark" | "light"
-  brandColor: "", // Hex color value
-  logo: "" // Absolute URL to logo image
-}
-```
-
-The hope is that with some minimal configuration / customization options, users won't immediately feel the need to replace the built-in pages with their own.
-
-More details and screenshots of the new theme options can be found under [custom pages tutorial](/guides/basics/pages).
-
-Introduced in https://github.com/nextauthjs/next-auth/pull/2788
-
-## Session
-
-The `session.jwt: boolean` option has been renamed to `session.strategy: "jwt" | "database"`. The goal is to make the user's options more intuitive:
-
-1. No adapter, `strategy: "jwt"`: This is the default. The session is saved in a cookie and never persisted anywhere.
-2. With Adapter, `strategy: "database"`: If an Adapter is defined, this will be the implicit setting. No user config is needed.
-3. With Adapter, `strategy: "jwt"`: The user can explicitly instruct `next-auth` to use JWT even if a database is available. This can result in faster lookups in compromise of lowered security. Read more about: https://authjs.dev/concepts/faq#json-web-tokens
-
-Example:
-
-```diff
-session: {
-- jwt: true,
-+ strategy: "jwt",
-}
-```
-
-Introduced in https://github.com/nextauthjs/next-auth/pull/3144
-
-## Adapters
-
-Most importantly, the core `next-auth` package no longer ships with `typeorm` or any other database adapter by default. This brings the default bundle size down significantly for those not needing to persist user data to a database.
-
-You can find the official Adapters in the `packages` directory in the primary monorepo ([nextauthjs/next-auth](https://github.com/nextauthjs/next-auth)). Although you can still [create your own](/guides/adapters/creating-a-database-adapter) with a new, [simplified Adapter API](https://github.com/nextauthjs/next-auth/pull/2361).
-
-If you have a database that was created with a `3.x.x` or earlier version of Auth.js, you will need to run a migration to update the schema to the new version 4 database model. See the bottom of this migration guide for database specific migration examples.
-
-1. If you use the built-in TypeORM or Prisma adapters, these have been removed from the core `next-auth` package. Thankfully the migration is easy; you just need to install the external packages for your database and change the import in your `[...nextauth].js`.
-
-The `database` option has been removed, you must now do the following instead:
-
-```diff
-// [...nextauth].js
-import NextAuth from "next-auth"
-+ import { TypeORMLegacyAdapter } from "@next-auth/typeorm-legacy-adapter"
-
-...
-export default NextAuth({
--  database: "yourconnectionstring",
-+  adapter: TypeORMLegacyAdapter("yourconnectionstring")
-})
-```
-
-2. The `prisma-legacy` adapter has been removed, please use the [`@next-auth/prisma-adapter`](https://npmjs.com/package/@next-auth/prisma-adapter) instead.
-
-3. The `typeorm-legacy` adapter has been upgraded to use the newer adapter API, but has retained the `typeorm-legacy` name. We aim to migrate this to individual lighter weight adapters for each database type in the future, or switch out `typeorm`.
-
-4. MongoDB has been moved to its own adapter under `@next-auth/mongodb-adapter`. See the [MongoDB Adapter docs](/reference/adapters/mongodb).
-
-Introduced in https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.8 and https://github.com/nextauthjs/next-auth/pull/2361
-
-### Adapter API
-
-**This does not require any changes from the user - these are adapter specific changes only**
-
-The Adapter API has been rewritten and significantly simplified in NextAuth v4. The adapters now have less work to do as some functionality has been migrated to the core of NextAuth, like hashing the [verification token](/reference/adapters/models/#verification-token).
-
-If you are an adapter maintainer or are interested in writing your own adapter, you can find more information about this change in https://github.com/nextauthjs/next-auth/pull/2361 and release https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-next.22.
-
-### Schema changes
-
-The way we save data with adapters have slightly changed. With the new Adapter API, we wanted to make it easier to extend your database with additional fields. For example if your User needs an extra `phone` field, it should be enough to add that to your database's schema, and no changes will be necessary in your adapter.
-
-- `created_at`/`createdAt` and `updated_at`/`updatedAt` fields are removed from all Models.
-- `user_id`/`userId` consistently named `userId`.
-- `compound_id`/`compoundId` is removed from Account.
-- `access_token`/`accessToken` is removed from Session.
-- `email_verified`/`emailVerified` on User is consistently named `emailVerified`.
-- `provider_id`/`providerId` renamed to `provider` on Account
-- `provider_type`/`providerType` renamed to `type` on Account
-- `provider_account_id`/`providerAccountId` on Account is consistently named `providerAccountId`
-- `access_token_expires`/`accessTokenExpires` on Account renamed to `expires_at`
-- New fields on Account: `token_type`, `scope`, `id_token`, `session_state`
-- `verification_requests` table has been renamed to `verification_tokens`
-
-<!-- REVIEW: Would something like this below be helpful? -->
-<details>
-<summary>
-See the changes
-</summary>
-<pre>
-
-```diff
-User {
-  id
-  name
-  email
-- emailVerified
-+ email_verified
-  image
--  created_at
--  updated_at
-}
-
-Account {
-  id
-- compound_id
-- user_id
-+ userId
--  provider_type
-+ type
-- provider_id
-+ provider
-- provider_account_id
-+ providerAccountId
-  refresh_token
-  access_token
-- access_token_expires
-+ expires_in
-+ expires_at
-+ token_type
-+ scope
-+ id_token
-+ session_state
-- created_at
-- updated_at
-}
-
-Session {
-  id
-  userId
-  expires
-  sessionToken
-- access_token
-- created_at
-- updated_at
-}
-
-VerificationToken {
-  id
-  token
-  expires
-  identifier
--  created_at
--  updated_at
-}
-```
-
-</pre>
-</details>
-
-For more info, see the [Models page](/reference/adapters/models).
-
-### Database migration
-
-Auth.js v4 has a slightly different database schema compared to v3. If you're using any of our adapters and want to upgrade, you can use on of the below schemas.
-
-They are designed to be run directly against the database itself. So instead of having one in Prisma syntax, one in TypeORM syntax, etc. we've decided to just make one for each underlying database type. i.e. one for Postgres, one for MySQL, one for MongoDB, etc.
-
-#### MySQL
-
-```sql
-/* ACCOUNT */
-ALTER TABLE accounts
-CHANGE "access_token_expires" "expires_at" int
-CHANGE "user_id" "userId" varchar(255)
-ADD CONSTRAINT fk_user_id FOREIGN KEY (userId) REFERENCES users(id)
-RENAME COLUMN "provider_id" "provider"
-RENAME COLUMN "provider_account_id" "providerAccountId"
-DROP COLUMN "provider_type"
-DROP COLUMN "compound_id"
-/* The following two timestamp columns have never been necessary for Auth.js to function, but can be kept if you want */
-DROP COLUMN "created_at"
-DROP COLUMN "updated_at"
-
-ADD COLUMN "token_type" varchar(255) NULL
-ADD COLUMN "scope" varchar(255) NULL
-ADD COLUMN "id_token" varchar(255) NULL
-ADD COLUMN "session_state" varchar(255) NULL
-
-/* Note: These are only needed if you're going to be using the old Twitter OAuth 1.0 provider. */
-ADD COLUMN "oauth_token_secret" varchar(255) NULL
-ADD COLUMN "oauth_token" varchar(255) NULL
-
-/* USER */
-ALTER TABLE users
-RENAME COLUMN "email_verified" "emailVerified"
-/* The following two timestamp columns have never been necessary for Auth.js to function, but can be kept if you want */
-DROP COLUMN "created_at"
-DROP COLUMN "updated_at"
-
-/* SESSION */
-ALTER TABLE sessions
-RENAME COLUMN "session_token" "sessionToken"
-CHANGE "user_id" "userId" varchar(255)
-ADD CONSTRAINT fk_user_id FOREIGN KEY (userId) REFERENCES users(id)
-DROP COLUMN "access_token"
-/* The following two timestamp columns have never been necessary for Auth.js to function, but can be kept if you want */
-DROP COLUMN "created_at"
-DROP COLUMN "updated_at"
-
-/* VERIFICATION REQUESTS */
-ALTER TABLE verification_requests RENAME verification_tokens
-ALTER TABLE verification_tokens
-DROP COLUMN id
-/* The following two timestamp columns have never been necessary for Auth.js to function, but can be kept if you want */
-DROP COLUMN "created_at"
-DROP COLUMN "updated_at"
-```
-
-#### Postgres
-
-```sql
-/* ACCOUNT */
-ALTER TABLE accounts RENAME COLUMN "user_id" TO "userId";
-ALTER TABLE accounts RENAME COLUMN "provider_id" TO "provider";
-ALTER TABLE accounts RENAME COLUMN "provider_account_id" TO "providerAccountId";
-ALTER TABLE accounts RENAME COLUMN "access_token_expires" TO "expires_at";
-ALTER TABLE accounts RENAME COLUMN "provider_type" TO "type";
-
-/* Do conversion of TIMESTAMPTZ to BIGINT */
-ALTER TABLE accounts ALTER COLUMN "expires_at" TYPE TEXT USING CAST(extract(epoch FROM "expires_at") AS BIGINT)*1000;
-
-/* Keep id as SERIAL with autoincrement when using ORM. Using new v4 uuid format won't work because of incompatibility */
-/* ALTER TABLE accounts ALTER COLUMN "id" TYPE TEXT; */
-/* ALTER TABLE accounts ALTER COLUMN "userId" TYPE TEXT; */
-ALTER TABLE accounts ALTER COLUMN "type" TYPE TEXT;
-ALTER TABLE accounts ALTER COLUMN "provider" TYPE TEXT;
-ALTER TABLE accounts ALTER COLUMN "providerAccountId" TYPE TEXT;
-
-ALTER TABLE accounts ADD CONSTRAINT fk_user_id FOREIGN KEY ("userId") REFERENCES users(id);
-ALTER TABLE accounts
-DROP COLUMN IF EXISTS "compound_id";
-/* The following two timestamp columns have never been necessary for Auth.js to function, but can be kept if you want */
-ALTER TABLE accounts
-DROP COLUMN IF EXISTS "created_at",
-DROP COLUMN IF EXISTS "updated_at";
-
-ALTER TABLE accounts
-ADD COLUMN IF NOT EXISTS "token_type" TEXT NULL,
-ADD COLUMN IF NOT EXISTS "scope" TEXT NULL,
-ADD COLUMN IF NOT EXISTS "id_token" TEXT NULL,
-ADD COLUMN IF NOT EXISTS "session_state" TEXT NULL;
-/* Note: These are only needed if you're going to be using the old Twitter OAuth 1.0 provider. */
-/* ALTER TABLE accounts
-ADD COLUMN IF NOT EXISTS "oauth_token_secret" TEXT NULL,
-ADD COLUMN IF NOT EXISTS "oauth_token" TEXT NULL; */
-
-/* USER */
-ALTER TABLE users RENAME COLUMN "email_verified" TO "emailVerified";
-
-/* Keep id as SERIAL with autoincrement when using ORM. Using new v4 uuid format won't work because of incompatibility */
-/* ALTER TABLE users ALTER COLUMN "id" TYPE TEXT; */
-ALTER TABLE users ALTER COLUMN "name" TYPE TEXT;
-ALTER TABLE users ALTER COLUMN "email" TYPE TEXT;
-ALTER TABLE users ALTER COLUMN "image" TYPE TEXT;
-/* Do conversion of TIMESTAMPTZ to BIGINT and then TEXT */
-ALTER TABLE users ALTER COLUMN "emailVerified" TYPE TEXT USING CAST(CAST(extract(epoch FROM "emailVerified") AS BIGINT)*1000 AS TEXT);
-/* The following two timestamp columns have never been necessary for Auth.js to function, but can be kept if you want */
-ALTER TABLE users
-DROP COLUMN IF EXISTS "created_at",
-DROP COLUMN IF EXISTS "updated_at";
-
-/* SESSION */
-ALTER TABLE sessions RENAME COLUMN "session_token" TO "sessionToken";
-ALTER TABLE sessions RENAME COLUMN "user_id" TO "userId";
-
-/* Keep id as SERIAL with autoincrement when using ORM. Using new v4 uuid format won't work because of incompatibility */
-/* ALTER TABLE sessions ALTER COLUMN "id" TYPE TEXT; */
-/* ALTER TABLE sessions ALTER COLUMN "userId" TYPE TEXT; */
-ALTER TABLE sessions ALTER COLUMN "sessionToken" TYPE TEXT;
-ALTER TABLE sessions ADD CONSTRAINT fk_user_id FOREIGN KEY ("userId") REFERENCES users(id);
-/* Do conversion of TIMESTAMPTZ to BIGINT and then TEXT */
-ALTER TABLE sessions ALTER COLUMN "expires" TYPE TEXT USING CAST(CAST(extract(epoch FROM "expires") AS BIGINT)*1000 AS TEXT);
-ALTER TABLE sessions DROP COLUMN IF EXISTS "access_token";
-/* The following two timestamp columns have never been necessary for Auth.js to function, but can be kept if you want */
-ALTER TABLE sessions
-DROP COLUMN IF EXISTS "created_at",
-DROP COLUMN IF EXISTS "updated_at";
-
-/* VERIFICATION REQUESTS */
-ALTER TABLE verification_requests RENAME TO verification_tokens;
-/* Keep id as ORM needs it */
-/* ALTER TABLE verification_tokens DROP COLUMN IF EXISTS id; */
-ALTER TABLE verification_tokens ALTER COLUMN "identifier" TYPE TEXT;
-ALTER TABLE verification_tokens ALTER COLUMN "token" TYPE TEXT;
-/* Do conversion of TIMESTAMPTZ to BIGINT and then TEXT */
-ALTER TABLE verification_tokens ALTER COLUMN "expires" TYPE TEXT USING CAST(CAST(extract(epoch FROM "expires") AS BIGINT)*1000 AS TEXT);
-/* The following two timestamp columns have never been necessary for Auth.js to function, but can be kept if you want */
-ALTER TABLE verification_tokens
-DROP COLUMN IF EXISTS "created_at",
-DROP COLUMN IF EXISTS "updated_at";
-```
-
-#### MongoDB
-
-MongoDB is a document database and as such new fields will be automatically populated. You do, however, need to update the names of existing fields which are going to be reused.
-
-```mongo
-db.getCollection('accounts').updateMany({}, {
-  $rename: {
-    "provider_id": "provider",
-    "provider_account_id": "providerAccountId",
-    "user_id": "userId",
-    "access_token_expires": "expires_at"
-  }
-})
-db.getCollection('users').updateMany({}, {
-  $rename: {
-    "email_verified": "emailVerified"
-  }
-})
-db.getCollection('sessions').updateMany({}, {
-  $rename: {
-    "session_token": "sessionToken",
-    "user_id": "userId"
-  }
-})
-```
-
-## Missing `secret`
-
-Auth.js used to generate a secret for convenience, when the user did not define one. This might have been useful in development, but can be a concern in production. We have always been clear about that in the docs, but from now on, if you forget to define a `secret` property in production, we will show the user an error page. Read more about this option [here](/reference/configuration/auth-config#secret)
-
-You can generate a secret to be placed in the `secret` configuration option via the following command:
-
-```bash
-$ openssl rand -base64 32
-```
-
-Therefore, your Auth.js config should look something like this:
-
-```javascript title="/pages/api/auth/[...nextauth].js"
-...
-export default NextAuth({
-  ...
-  providers: [...],
-  secret: "LlKq6ZtYbr+hTC073mAmAh9/h2HwMfsFo4hrfCx5mLg=",
-  ...
-})
-```
-
-Introduced in https://github.com/nextauthjs/next-auth/issues/3143
-
-## Session `strategy`
-
-We have always supported two different session strategies. The first being our most popular and default strategy - the JWT based one. The second is the database adapter persisted session strategy. Both have their advantages/disadvantages, you can learn more about them on the [FAQ](/concepts/faq) page.
-
-Previously, the way you configured this was through the `jwt: boolean` flag in the `session` option. The names `session` and `jwt` might have been a bit overused in the options, and so for a clearer message, we renamed this option to `strategy: "jwt" | "database"`, it is still in the `session` object. This will hopefully better indicate the purpose of this option as well as make very explicit which type of session you are going to use.
-
-See the [`session` option docs](/reference/configuration/auth-config#session) for more details.
-
-Introduced in https://github.com/nextauthjs/next-auth/pull/3144
-
-## Summary
-
-We hope this migration goes smoothly for each and every one of you! If you have any questions or get stuck anywhere, feel free to create [a new issue](https://github.com/nextauthjs/next-auth/issues/new) on GitHub.

docs/docs/getting-started/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Getting Started",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/guides/03-basics/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Basics",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/guides/03-basics/role-based-access-control.md

@@ -1,153 +0,0 @@
----
-title: Role-based access control
----
-
-There are two ways to add role-based access control (RBAC) to your application, based on the [session strategy](/concepts/session-strategies) you choose. Let's see an example for each of these.
-
-## Getting the role
-
-We are going to start by adding a `profile()` callback to the providers' config to determine the user role:
-
-```ts title="/pages/api/auth/[...nextauth].ts"
-import NextAuth from "next-auth"
-import Google from "next-auth/providers/google"
-
-export default NextAuth({
-  providers: [
-    Google({
-      profile(profile) {
-        return { role: profile.role ?? "user", ... }
-      },
-      ...
-    })  
-  ],
-})
-```
-
-:::tip
-To determine the user's role, you can either add your logic or if your provider assigns roles already, use that instead.
-:::
-
-## Persisting the role
-### With JWT
-
-When you don't have a database configured, the role will be persisted in a cookie, by using the `jwt()` callback. On sign-in, the `role` property is exposed from the `profile` callback on the `user` object. Persist the `user.role` value by assigning it to `token.role`. That's it!
-
-If you also want to use the role on the client, you can expose it via the `session` callback.
-
-```ts title="/pages/api/auth/[...nextauth].ts"
-import NextAuth from "next-auth"
-import Google from "next-auth/providers/google"
-
-export default NextAuth({
-  providers: [
-    Google({
-      profile(profile) {
-        return { role: profile.role ?? "user", ... }
-      },
-      ...
-    })  
-  ],
-  // highlight-start
-  callbacks: {
-    jwt({ token, user }) {
-      if(user) token.role = user.role
-      return token
-    },
-    session({ session, token }) {
-      session.user.role = token.role
-      return session
-    }
-  }
-  // highlight-end
-})
-```
-
-:::info
-With this strategy, if you want to update the role, the user needs to be forced to sign in again.
-:::
-
-### With Database
-
-When you have a database, you can save the user role on the [User model](/reference/adapters/models#user). The below example is showing you how to do this with Prisma, but the idea is the same for all adapters.
-
-First, add a `role` column to the User model.
-
-```ts title="/prisma/schema.prisma"
-model User {
-  id            String    @id @default(cuid())
-  name          String?
-  email         String?   @unique
-  emailVerified DateTime?
-  image         String?
-  role          String?  // New column
-  accounts      Account[]
-  sessions      Session[]
-}
-```
-
-The `profile()` callback's return value is used to create users in the database. That's it! Your newly created users will now have an assigned role.
-
-If you also want to use the role on the client, you can expose it via the `session` callback.
-
-```ts title="/pages/api/auth/[...nextauth].ts"
-import NextAuth from "next-auth"
-import Google from "next-auth/providers/google"
-  // highlight-next-line
-import prisma from "lib/prisma"
-
-export default NextAuth({
-  // highlight-next-line
-  adapter: PrismaAdapter(prisma),
-  providers: [
-    Google({
-      profile(profile) {
-        return { role: profile.role ?? "user", ... }
-      }
-      ...
-    })  
-  ],
-  // highlight-start
-  callbacks: {
-    session({ session, user }) {
-      session.user.role = user.role
-      return session
-    }
-  }
-  // highlight-end
-})
-```
-
-:::info
-It is up to you how you want to manage to update the roles, either through direct database access or building your role update API.
-:::
-
-## Using the role
-
-If you want to use the role in the client, for both cases above, when using the `useSession` hook, `session.user.role` will have the required role if you exposed it via the `session` callback. You can use this to render a different UI for different users.
-
-```ts title="/pages/admin.tsx"
-import { useSession } from "next-auth/react"
-
-export default function Page() {
-  const session = await useSession()
-
-  if (session?.user.role === "admin") {
-    return <p>You are an admin, welcome!</p>
-  }
-
-  return <p>You are not authorized to view this page!</p>
-}
-```
-
-:::tip
-When using Next.js and JWT, you can alternatively also use [Middleware](https://next-auth.js.org/configuration/nextjs#wrap-middleware) to redirect the user based on their role, even before rendering the page.
-:::
-
-## Resources
-
-- [Concepts: Session strategies](/concepts/session-strategies)
-- [Next.js: Middleware](https://next-auth.js.org/configuration/nextjs#wrap-middleware)
-- [Adapters: User model](/reference/adapters/models#user)
-- [Adapters: Prisma adapter](/reference/adapters/prisma)
-- [TypeScript](/getting-started/typescript)

docs/docs/guides/04-providers/03-email-http-api.md

@@ -1,109 +0,0 @@
----
-id: email-http
-title: HTTP-based Email Provider
----
-
-## Introduction
-
-:::note
-The following guide is written for `next-auth` (NextAuth.js), but it should work for any of the Auth.js framework libraries (`@auth/*`) as well.
-:::
-
-
-There is a built-in Email provider with which you could connect to the SMTP server of your choice to send "magic link" emails for sign-in purposes. However, the Email provider can also be used with HTTP-based email services, like AWS SES, Postmark, Sendgrid, etc. In this guide, we are going to explain how to use our Email magic link provider with any of the more modern HTTP-based Email APIs.
-
-For this example, we will be using [SendGrid](https://sendgrid.com), but any email service providing an HTTP API or JS client library will work.
-We will also refer to the [Prisma Adapter](/reference/adapter/prisma). A [database adapter](/adapters/overview) is a requirement for the Email provider.
-
-## Setup
-
-First, if you do not have a project using Auth.js, clone and set up a basic Auth.js project like the one [provided in](https://github.com/nextauthjs/next-auth-example.git) our example repo](https://github.com/nextauthjs/next-auth-example.git).
-
-- Install the [Prisma Adapter](/reference/adapter/prisma)
-- Generate an API key from your cloud Email provider of choice and add it to your `.env.*` file. For example, mine is going to be called `SENDGRID_API`
-- Add the following configuration to your configuration file:
-
-```js title="pages/api/auth/[...nextauth].ts"
-import NextAuth, { NextAuthOptions } from "next-auth"
-import { PrismaAdapter } from "@next-auth/prisma-adapter"
-import { PrismaClient } from "@prisma/client"
-
-const prisma = new PrismaClient()
-
-export const authOptions: NextAuthOptions = {
-  adapter: PrismaAdapter(prisma),
-  providers: [
-    {
-      id: 'sendgrid',
-      type: 'email',
-      async sendVerificationRequest({identifier: email, url}) {
-      }
-    }
-  ],
-}
-
-export default NextAuth(authOptions)
-```
-
-Next, all that's left to do is call the HTTP endpoint from our cloud email provider and pass it the required metadata like the `to` address, the email `body`, and any other fields we may need to include.
-
-As mentioned earlier, we're going to be using SendGrid in this example, so the appropriate endpoint is `https://api.sendgrid.com/v3/mail/send` ([more info](https://docs.sendgrid.com/for-developers/sending-email/api-getting-started)). Therefore, we're going to pull out some of the important information from the `params` argument and use it in a `fetch()` call to the previously mentioned SendGrid API.
-
-```js title="pages/api/auth/[...nextauth].ts"
-import NextAuth, { NextAuthOptions } from "next-auth"
-import { PrismaAdapter } from "@next-auth/prisma-adapter"
-import { PrismaClient } from "@prisma/client"
-
-const prisma = new PrismaClient()
-
-export const authOptions: NextAuthOptions = {
-  adapter: PrismaAdapter(prisma),
-  providers: [
-    {
-      id: 'sendgrid',
-      type: 'email',
-      async sendVerificationRequest({identifier: email, url}) {
-        // highlight-start
-        // Call the cloud Email provider API for sending emails
-        // See https://docs.sendgrid.com/api-reference/mail-send/mail-send
-        const response = await fetch("https://api.sendgrid.com/v3/mail/send", {
-          // The body format will vary depending on provider, please see their documentation
-          // for further details.
-          body: JSON.stringify({
-            personalizations: [{ to: [{ email }] }],
-            from: { email: "noreply@company.com" },
-            subject: "Sign in to Your page",
-            content: [
-              {
-                type: "text/plain",
-                value: `Please click here to authenticate - ${url}`,
-              },
-            ],
-          }),
-          headers: {
-            // Authentication will also vary from provider to provider, please see their docs.
-            Authorization: `Bearer ${process.env.SENDGRID_API}`,
-            "Content-Type": "application/json",
-          },
-          method: "POST",
-        })
-
-        if (!response.ok) {
-          const { errors } = await response.json()
-          throw new Error(JSON.stringify(errors))
-        }
-        // highlight-end
-      },
-    }
-  ],
-}
-```
-
-And that's all we need to do to send Emails via an HTTP API! Note here that the example is only using `text/plain` as the body type. You'll probably want to change that to `text/html` and pass in a nice-looking HTML email. See, for example, our `html` function in [the Auth.js docs](/providers/email#customizing-emails).
-
-To sign in via this custom provider, you would refer to it by the `id` in when you are calling the sign-in method, for example: `signIn('sendgrid', { email: 'user@company.com' })`.
-
-## References
-
-- [Email provider documentation with HTML generation and more](/reference/core/modules/providers_email)
-- [SendGrid JSON Body documentation](https://docs.sendgrid.com/api-reference/mail-send/mail-send#body)

docs/docs/guides/04-providers/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Providers",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/guides/05-adapters/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Adapters",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/guides/06-testing/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Testing",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/guides/07-corporate-proxies/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Corporate proxies",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/guides/08-other/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Other",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/guides/09-resources.md

@@ -1,118 +0,0 @@
----
-id: resources
-title: Community resources
----
-
-> These tutorials are contributed by the community.
-> **New submissions and edits are welcome!**
-
-## Basics
-
-#### [Introduction to Auth.js](https://www.youtube.com/watch?v=npZsJxWntJM) <svg role="img" viewBox="0 0 24 24" height="24" width="24" style={{ marginLeft: '5px', marginBottom:'-6px'}} xmlns="http://www.w3.org/2000/svg"><title>YouTube</title><path fill="#ff0000" d="M23.498 6.186a3.016 3.016 0 0 0-2.122-2.136C19.505 3.545 12 3.545 12 3.545s-7.505 0-9.377.505A3.017 3.017 0 0 0 .502 6.186C0 8.07 0 12 0 12s0 3.93.502 5.814a3.016 3.016 0 0 0 2.122 2.136c1.871.505 9.376.505 9.376.505s7.505 0 9.377-.505a3.015 3.015 0 0 0 2.122-2.136C24 15.93 24 12 24 12s0-3.93-.502-5.814zM9.545 15.568V8.432L15.818 12l-6.273 3.568z"/></svg>
-
-- This is an introductory video to Auth.js for beginners. In this video, it is explained how to set up authentication in a few easy steps and add different configurations to make it more robust and secure.
-
-#### [Authentication patterns for Next.js](https://nextjs.org/docs/authentication) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title><path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- Next.js supports multiple patterns for authentication, each designed for different use cases. This guide will allow you to choose your adventure based on your constraints. By Lee Robinson.
-
-#### [Adding Authentication to an existing Next.js Application in no time!](https://dev.to/ndom91/adding-authentication-to-an-existing-serverless-next-js-app-in-no-time-with-nextauth-js-192h) <svg style={{ marginLeft: '5px', marginBottom:'-6px'}} width="30" height="25" viewBox="0 0 50 40" fill="none" xmlns="http://www.w3.org/2000/svg"><rect width="50" height="40" rx="3" style={{ fill: '#000' }}></rect><path d="M19.099 23.508c0 1.31-.423 2.388-1.27 3.234-.838.839-1.942 1.258-3.312 1.258h-4.403V12.277h4.492c1.31 0 2.385.423 3.224 1.27.846.838 1.269 1.912 1.269 3.223v6.738zm-2.808 0V16.77c0-.562-.187-.981-.562-1.258-.374-.285-.748-.427-1.122-.427h-1.685v10.107h1.684c.375 0 .75-.138 1.123-.415.375-.285.562-.708.562-1.27zM28.185 28h-5.896c-.562 0-1.03-.187-1.404-.561-.375-.375-.562-.843-.562-1.404V14.243c0-.562.187-1.03.562-1.404.374-.375.842-.562 1.404-.562h5.896v2.808H23.13v3.65h3.088v2.808h-3.088v3.65h5.054V28zm7.12 0c-.936 0-1.684-.655-2.246-1.965l-3.65-13.758h3.089l2.807 10.804 2.808-10.804H41.2l-3.65 13.758C36.99 27.345 36.241 28 35.305 28z" style={{ fill: '#fff' }}></path></svg>
-
-- This tutorial walks one through adding Auth.js to an existing project. Including setting up the OAuth client id and secret, adding the API routes for authentication, protecting pages and API routes behind that authentication, etc.
-
-#### [Adding social authentication support to a Next.js app](https://getstarted.sh/bulletproof-next/add-social-authentication) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- A tutorial by Arunoda Susirpiala. Checkout [GetStarted](https://getstarted.sh/) for more examples.
-
-#### [How to Authenticate Next.js Apps with Twitter & Auth.js](https://spacejelly.dev/posts/how-to-authenticate-next-js-apps-with-twitter-nextauth-js/) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- Learn how to add Twitter authentication and login to a Next.js app both client-side and server-side with Auth.js.
-
-#### [NextJS Authentication Crash Course with Auth.js](https://youtu.be/o_wZIVmWteQ) <svg role="img" viewBox="0 0 24 24" height="24" width="24" style={{ marginLeft: '5px', marginBottom:'-6px'}} xmlns="http://www.w3.org/2000/svg"><title>YouTube</title><path fill="#ff0000" d="M23.498 6.186a3.016 3.016 0 0 0-2.122-2.136C19.505 3.545 12 3.545 12 3.545s-7.505 0-9.377.505A3.017 3.017 0 0 0 .502 6.186C0 8.07 0 12 0 12s0 3.93.502 5.814a3.016 3.016 0 0 0 2.122 2.136c1.871.505 9.376.505 9.376.505s7.505 0 9.377-.505a3.015 3.015 0 0 0 2.122-2.136C24 15.93 24 12 24 12s0-3.93-.502-5.814zM9.545 15.568V8.432L15.818 12l-6.273 3.568z"/></svg>
-
-- This tutorial dives into the ins and outs of NextAuth, including using the Email, Github, Twitter and Auth0 providers in under an hour.
-
-#### [Create your own Auth.js Login Pages](https://youtu.be/kB6YNYZ63fw) <svg role="img" viewBox="0 0 24 24" height="24" width="24" style={{ marginLeft: '5px', marginBottom:'-6px'}} xmlns="http://www.w3.org/2000/svg"><title>YouTube</title><path fill="#ff0000" d="M23.498 6.186a3.016 3.016 0 0 0-2.122-2.136C19.505 3.545 12 3.545 12 3.545s-7.505 0-9.377.505A3.017 3.017 0 0 0 .502 6.186C0 8.07 0 12 0 12s0 3.93.502 5.814a3.016 3.016 0 0 0 2.122 2.136c1.871.505 9.376.505 9.376.505s7.505 0 9.377-.505a3.015 3.015 0 0 0 2.122-2.136C24 15.93 24 12 24 12s0-3.93-.502-5.814zM9.545 15.568V8.432L15.818 12l-6.273 3.568z"/></svg>
-
-- This tutorial shows you how to jump in and create your own custom login pages versus using the ones provided by Auth.js
-
-#### [Passwordless Authentication with next-auth](https://www.youtube.com/watch?v=GPBD3acOx_M) <svg role="img" viewBox="0 0 24 24" height="24" width="24" style={{ marginLeft: '5px', marginBottom:'-6px'}} xmlns="http://www.w3.org/2000/svg"><title>YouTube</title><path fill="#ff0000" d="M23.498 6.186a3.016 3.016 0 0 0-2.122-2.136C19.505 3.545 12 3.545 12 3.545s-7.505 0-9.377.505A3.017 3.017 0 0 0 .502 6.186C0 8.07 0 12 0 12s0 3.93.502 5.814a3.016 3.016 0 0 0 2.122 2.136c1.871.505 9.376.505 9.376.505s7.505 0 9.377-.505a3.015 3.015 0 0 0 2.122-2.136C24 15.93 24 12 24 12s0-3.93-.502-5.814zM9.545 15.568V8.432L15.818 12l-6.273 3.568z"/></svg>
-
-- A video tutorial by Xiaoru Li from Prisma.
-
-#### [How to authenticate Next.js Apps with Sign-In With Ethereum (SIWE) & Auth.js](https://docs.login.xyz/integrations/Auth.js) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- Learn how to use Sign-In With Ethereum to authenticate your users with their existing Ethereum wallets - identifiers they personally control.
-- Example application: [spruceid/siwe-next-auth-example](https://github.com/spruceid/siwe-next-auth-example)
-
-#### [Next.js Authentication with Okta and Auth.js 4.0](https://thetombomb.com/posts/nextjs-nextauth-okta) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- Learn how to perform authentication with an OIDC Application in Okta and Auth.js.
-
-## Fullstack
-
-#### [Build a FullStack App with Next.js, Auth.js, Supabase & Prisma](https://themodern.dev/courses/build-a-fullstack-app-with-nextjs-supabase-and-prisma-322389284337222224) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-In this [free course](https://themodern.dev/courses/build-a-fullstack-app-with-nextjs-supabase-and-prisma-322389284337222224), you'll learn how to build a full-stack app using the following technologies:
-
-- **Next.js** - The React framework for building the UI of the app and the REST API
-- **Auth.js** - For implementing passwordless and OAuth authentication
-- **Supabase** - For persisting the app data into a PostgreSQL database and storing media files
-- **Prisma** - For making it easy to read and write data from our app from and to the database
-
-The app that we'll work on in this course is called **_SupaVacation_**. It is an online marketplace for vacation rentals where users can browse through all the properties for rent, bookmark their favorite ones, and even rent their own properties.
-
-> Here's [a live demo](https://supa-vacation.vercel.app/) of the app's final version. It is what your app should look likes after completing this course. Feel free to play with it to get an overview of all the features you'll be working on.
-
-#### [Magic Link Authentication in Next.js with NextAuth and Fauna](https://alterclass.io/tutorials/magic-link-authentication-in-nextjs-with-nextauth-and-fauna) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-Learn how to implement passwordless/magic link authentication with database storage in your Next.js projects using NextAuth and Fauna DB.
-
-> The final version of the project's code can be found on [Github](https://github.com/AlterClassIO/magic-next-auth). You can use it as a starting point for any Next.js app that requires passwordless authentication.
-
-> You can also preview the example live [here](https://magic-next-auth.vercel.app/).
-
-This tutorial covers:
-
-- Configuring Next.js, Auth.js, and Fauna to work together seamlessly
-- Using Next.js dynamic API routes to handle authentication requests
-- Using Fauna and the Fauna Adapter for `next-auth` to persist users, email sign in tokens, and sessions
-- Creating custom login and confirmation pages with React + Tailwind CSS
-- Customizing the sign-in email and sending a welcome email to new users
-
-#### [Passwordless Authentication with Next.js, Prisma, and next-auth](https://dev.to/prisma/passwordless-authentication-with-next-js-prisma-and-next-auth-5g8g) <svg style={{ marginLeft: '5px', marginBottom:'-6px'}} width="30" height="25" viewBox="0 0 50 40" fill="none" xmlns="http://www.w3.org/2000/svg"><rect width="50" height="40" rx="3" style={{ fill: '#000' }}></rect><path d="M19.099 23.508c0 1.31-.423 2.388-1.27 3.234-.838.839-1.942 1.258-3.312 1.258h-4.403V12.277h4.492c1.31 0 2.385.423 3.224 1.27.846.838 1.269 1.912 1.269 3.223v6.738zm-2.808 0V16.77c0-.562-.187-.981-.562-1.258-.374-.285-.748-.427-1.122-.427h-1.685v10.107h1.684c.375 0 .75-.138 1.123-.415.375-.285.562-.708.562-1.27zM28.185 28h-5.896c-.562 0-1.03-.187-1.404-.561-.375-.375-.562-.843-.562-1.404V14.243c0-.562.187-1.03.562-1.404.374-.375.842-.562 1.404-.562h5.896v2.808H23.13v3.65h3.088v2.808h-3.088v3.65h5.054V28zm7.12 0c-.936 0-1.684-.655-2.246-1.965l-3.65-13.758h3.089l2.807 10.804 2.808-10.804H41.2l-3.65 13.758C36.99 27.345 36.241 28 35.305 28z" style={{ fill: '#fff' }}></path></svg>
-
-- In this post, you'll learn how to add passwordless authentication to your Next.js app using Prisma and next-auth. By the end of this tutorial, your users will be able to log in to your app with either their GitHub account or a Slack-styled magic link sent right to their Email inbox. By Xiaoru Li.
-
-#### [Fullstack Authentication Example with Next.js and Auth.js](https://github.com/prisma/prisma-examples/tree/latest/typescript/rest-nextjs-api-routes-auth) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- This example shows how to implement a full-stack app in TypeScript with Next.js using Prisma Client as a backend. It also demonstrates how to implement authentication using Auth.js. By Nikolas Burk at Prisma.
-
-## Advanced
-
-#### [Add auth support to a Next.js app with a custom backend](https://arunoda.me/blog/add-auth-support-to-a-next-js-app-with-a-custom-backend) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- A tutorial by Arunoda Susirpiala.
-
-#### [How to Configure Azure AD B2C Authentication with Next.js](https://benjaminwfox.com/blog/tech/how-to-configure-azure-b2c-with-nextjs) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- Configuring authentication with Azure B2C in Next.js is not a particularly straight forward process. We'll look at how to facilitate this using the Auth.js library. By Ben Fox.
-
-#### [Sign in with Apple in NextJS](https://thesiddd.com/blog/apple-auth) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- This tutorial walks step by step on how to get sign in with Apple working (both locally and on a deployed website) using Auth.js.
-
-#### [Using Auth.js with Magic links](https://dev.to/narciero/using-nextauth-js-with-magic-links-df4) <svg style={{ marginLeft: '5px', marginBottom:'-6px'}} width="30" height="25" viewBox="0 0 50 40" fill="none" xmlns="http://www.w3.org/2000/svg"><rect width="50" height="40" rx="3" style={{ fill: '#000' }}></rect><path d="M19.099 23.508c0 1.31-.423 2.388-1.27 3.234-.838.839-1.942 1.258-3.312 1.258h-4.403V12.277h4.492c1.31 0 2.385.423 3.224 1.27.846.838 1.269 1.912 1.269 3.223v6.738zm-2.808 0V16.77c0-.562-.187-.981-.562-1.258-.374-.285-.748-.427-1.122-.427h-1.685v10.107h1.684c.375 0 .75-.138 1.123-.415.375-.285.562-.708.562-1.27zM28.185 28h-5.896c-.562 0-1.03-.187-1.404-.561-.375-.375-.562-.843-.562-1.404V14.243c0-.562.187-1.03.562-1.404.374-.375.842-.562 1.404-.562h5.896v2.808H23.13v3.65h3.088v2.808h-3.088v3.65h5.054V28zm7.12 0c-.936 0-1.684-.655-2.246-1.965l-3.65-13.758h3.089l2.807 10.804 2.808-10.804H41.2l-3.65 13.758C36.99 27.345 36.241 28 35.305 28z" style={{ fill: '#fff' }}></path></svg>
-
-- Learn how to use [Magic.Link](https://magic.link) authentication with [Auth.js](https://authjs.dev) to enable passwordless authentication without a database.
-
-## Database
-
-#### [Create a Auth.js Custom Adapter with HarperDB & Next.js](https://spacejelly.dev/posts/how-to-create-a-nextauth-js-custom-adapter-with-harperdb-next-js/) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- Use a custom database in a Custom Adapter for persisted Auth.js sessions using HarperDB as an example.
-- Video tutorial also available: <https://www.youtube.com/watch?v=pu7xBv7sZ8s>
-
-#### [Using Auth.js with Prisma and PlanetScale serverless databases](https://github.com/planetscale/nextjs-planetscale-starter) <svg xmlns="http://www.w3.org/2000/svg" style={{ marginLeft: '5px', marginBottom:'-6px'}} height="20" width="20" fill="none" viewBox="0 0 24 24" stroke="currentColor"><title>External</title> <path strokeLinecap="round" strokeLinejoin="round" strokeWidth="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14" /> </svg>
-
-- How to set up a PlanetScale database to fetch and store user / account data with the Prisma adapter.

docs/docs/reference/02-configuration/01-auth-config.md

@@ -1,447 +0,0 @@
----
-title: Initialization
----
-
-## Options
-
-Options are passed to Auth.js when initializing it in a server environment like a Next.js API Route.
-
-### providers
-
-- **Default value**: `[]`
-- **Required**: _Yes_
-
-#### Description
-
-An array of authentication providers for signing in (e.g. Google, Facebook, Twitter, GitHub, Email, etc) in any order. This can be one of the built-in providers or an object with a custom provider.
-
-Refer to the list of [all available Oauth providers](/reference/providers/oauth-builtin) and the [Oauth tutorial](/getting-started/oauth-tutorial) on how to use them.
-
----
-
-### secret
-
-- **Default value**: `string` (_SHA hash of the "options" object_) in development, no default in production.
-- **Required**: _Yes, in production!_
-
-#### Description
-
-A random string is used to hash tokens, sign/encrypt cookies and generate cryptographic keys.
-
-If you set [`NEXTAUTH_SECRET`](#nextauth_secret) as an environment variable, you don't have to define this option.
-
-If no value specified specified in development (and there is no `NEXTAUTH_SECRET` variable either), it uses a hash for all configuration options, including OAuth Client ID / Secrets for entropy.
-
-:::warning
-Not providing any `secret` or `NEXTAUTH_SECRET` will throw [an error](/reference/errors#no_secret) in production.
-:::
-
-You can quickly create a good value on the command line via this `openssl` command.
-
-```bash
-$ openssl rand -base64 32
-```
-
-:::tip
-If you rely on the default secret generation in development, you might notice JWT decryption errors, since the secret changes whenever you change your configuration. Defining an explicit secret will make this problem go away. We will likely make this option mandatory, even in development, in the future.
-:::
-
----
-
-### session
-
-- **Default value**: `object`
-- **Required**: _No_
-
-#### Description
-
-The `session` object and all properties on it are optional.
-
-Default values for this option are shown below:
-
-```js
-session: {
-  // Choose how you want to save the user session.
-  // The default is `"jwt"`, an encrypted JWT (JWE) stored in the session cookie.
-  // If you use an `adapter` however, we default it to `"database"` instead.
-  // You can still force a JWT session by explicitly defining `"jwt"`.
-  // When using `"database"`, the session cookie will only contain a `sessionToken` value,
-  // which is used to look up the session in the database.
-  strategy: "database",
-
-  // Seconds - How long until an idle session expires and is no longer valid.
-  maxAge: 30 * 24 * 60 * 60, // 30 days
-
-  // Seconds - Throttle how frequently to write to database to extend a session.
-  // Use it to limit write operations. Set to 0 to always update the database.
-  // Note: This option is ignored if using JSON Web Tokens
-  updateAge: 24 * 60 * 60, // 24 hours
-}
-```
-
----
-
-### jwt
-
-- **Default value**: `object`
-- **Required**: _No_
-
-#### Description
-
-JSON Web Tokens can be used for session tokens if enabled with `session: { strategy: "jwt" }` option. JSON Web Tokens are enabled by default if you have not specified an adapter. JSON Web Tokens are encrypted (JWE) by default. We recommend you keep this behaviour. See the [Override JWT `encode` and `decode` methods](#override-jwt-encode-and-decode-methods) advanced option.
-
-#### JSON Web Token Options
-
-```js
-jwt: {
-  // The maximum age of the Auth.js issued JWT in seconds.
-  // Defaults to `session.maxAge`.
-  maxAge: 60 * 60 * 24 * 30,
-  // You can define your own encode/decode functions for signing and encryption
-  async encode() {},
-  async decode() {},
-}
-```
-
-An example JSON Web Token contains a payload like this:
-
-```js
-{
-  name: 'Iain Collins',
-  email: 'me@iaincollins.com',
-  picture: 'https://example.com/image.jpg',
-  iat: 1594601838,
-  exp: 1597193838
-}
-```
-
-#### JWT Helper
-
-You can use the built-in `getToken()` helper method to verify and decrypt the token, like this:
-
-```js
-import { getToken } from "next-auth/jwt"
-
-const secret = process.env.NEXTAUTH_SECRET
-
-export default async function handler(req, res) {
-  // if using `NEXTAUTH_SECRET` env variable, we detect it, and you won't actually need to `secret`
-  // const token = await getToken({ req })
-  const token = await getToken({ req, secret })
-  console.log("JSON Web Token", token)
-  res.end()
-}
-```
-
-_For convenience, this helper function is also able to read and decode tokens passed from the `Authorization: 'Bearer token'` HTTP header._
-
-**Required**
-
-The getToken() helper requires the following options:
-
-- `req` - (object) Request object
-- `secret` - (string) JWT Secret. Use `NEXTAUTH_SECRET` instead.
-
-You must also pass _any options configured on the `jwt` option_ to the helper.
-
-e.g. Including custom session `maxAge` and custom signing and/or encryption keys or options
-
-**Optional**
-
-It also supports the following options:
-
-- `secureCookie` - (boolean) Use secure prefixed cookie name
-
-  By default, the helper function will attempt to determine if it should use the secure prefixed cookie (e.g. `true` in production and `false` in development, unless NEXTAUTH_URL contains an HTTPS URL).
-
-- `cookieName` - (string) Session token cookie name
-
-  The `secureCookie` option is ignored if `cookieName` is explicitly specified.
-
-- `raw` - (boolean) Get raw token (not decoded)
-
-  If set to `true` returns the raw token without decrypting or verifying it.
-
-:::note
-The JWT is stored in the Session Token cookie, the same cookie used for tokens with database sessions.
-:::
-
----
-
-### pages
-
-- **Default value**: `{}`
-- **Required**: _No_
-
-#### Description
-
-Specify URLs to be used if you want to create custom sign in, sign out and error pages.
-
-Pages specified will override the corresponding built-in page.
-
-_For example:_
-
-```js
-pages: {
-  signIn: '/auth/signin',
-  signOut: '/auth/signout',
-  error: '/auth/error', // Error code passed in query string as ?error=
-  verifyRequest: '/auth/verify-request', // (used for check email message)
-  newUser: '/auth/new-user' // New users will be directed here on first sign in (leave the property out if not of interest)
-}
-```
-
-:::note
-When using this configuration, ensure that these pages actually exist. For example `error: '/auth/error'` refers to a page file at `pages/auth/error.js`.
-:::
-
-See the documentation for the [creating custom pages guide](/guides/basics/pages) for more information.
-
----
-
-### callbacks
-
-- **Default value**: `object`
-- **Required**: _No_
-
-#### Description
-
-Callbacks are asynchronous functions you can use to control what happens when an action is performed.
-
-Callbacks are extremely powerful, especially in scenarios involving JSON Web Tokens as they allow you to implement access controls without a database and to integrate with external databases or APIs.
-
-You can specify a handler for any of the callbacks below.
-
-```js
-callbacks: {
-  async signIn({ user, account, profile, email, credentials }) {
-    return true
-  },
-  async redirect({ url, baseUrl }) {
-    return baseUrl
-  },
-  async session({ session, token, user }) {
-    return session
-  },
-  async jwt({ token, user, account, profile, isNewUser }) {
-    return token
-  }
-}
-```
-
-See [our callbacks guide](/guides/basics/callbacks) for more information on how to use the callback functions.
-
----
-
-### events
-
-- **Default value**: `object`
-- **Required**: _No_
-
-#### Description
-
-Events are asynchronous functions that do not return a response, they are useful for audit logging.
-
-You can specify a handler for any of these events below - e.g. for debugging or to create an audit log.
-
-The content of the message object varies depending on the flow (e.g. OAuth or Email authentication flow, JWT or database sessions, etc). See the [events guide](/guides/basics/events) for more information on the form of each message object and how to use the events functions.
-
-```js
-events: {
-  async signIn(message) { /* on successful sign in */ },
-  async signOut(message) { /* on signout */ },
-  async createUser(message) { /* user created */ },
-  async updateUser(message) { /* user updated - e.g. their email was verified */ },
-  async linkAccount(message) { /* account (e.g. Twitter) linked to a user */ },
-  async session(message) { /* session is active */ },
-}
-```
-
----
-
-### adapter
-
-- **Default value**: none
-- **Required**: _No_
-
-#### Description
-
-By default Auth.js does not include an adapter any longer. If you would like to persist user / account data, please install one of the many available adapters. More information can be found in the [adapter documentation](/reference/adapters/overview).
-
----
-
-### debug
-
-- **Default value**: `false`
-- **Required**: _No_
-
-#### Description
-
-Set debug to `true` to enable debug messages for authentication and database operations.
-
----
-
-### logger
-
-- **Default value**: `console`
-- **Required**: _No_
-
-#### Description
-
-Override any of the logger levels (`undefined` levels will use the built-in logger), and intercept logs in NextAuth. You can use this to send NextAuth logs to a third-party logging service.
-
-The `code` parameter for `error` and `warn` are explained in the [Warnings](/reference/warnings) and [Errors](/reference/errors) pages respectively.
-
-Example:
-
-```js title="/pages/api/auth/[...nextauth].js"
-import log from "logging-service"
-
-export default NextAuth({
-  ...
-  logger: {
-    error(code, metadata) {
-      log.error(code, metadata)
-    },
-    warn(code) {
-      log.warn(code)
-    },
-    debug(code, metadata) {
-      log.debug(code, metadata)
-    }
-  }
-  ...
-})
-```
-
-:::note
-If the `debug` level is defined by the user, it will be called regardless of the `debug: false` [option](#debug).
-:::
-
----
-
-### theme
-
-- **Default value**: `object`
-- **Required**: _No_
-
-#### Description
-
-Changes the color scheme theme of [pages](/reference/configuration/auth-config#pages) as well as allows some minor customization. Set `theme.colorScheme` to `"light"`, if you want to force pages to always be light. Set to `"dark"`, if you want to force pages to always be dark. Set to `"auto"`, (or leave this option out) if you want the pages to follow the preferred system theme. (Uses the [prefers-color-scheme](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme) media query.)
-
-In addition, you can define a logo URL in `theme.logo` which will be rendered above the main card in the default signin/signout/error/verify-request pages, as well as a `theme.brandColor` which will affect the accent color of these pages.
-
-```js
-theme: {
-  colorScheme: "auto", // "auto" | "dark" | "light"
-  brandColor: "", // Hex color code
-  logo: "" // Absolute URL to image
-}
-```
-
----
-
-## Advanced Options
-
-Advanced options are passed the same way as basic options, but may have complex implications or side effects. You should try to avoid using advanced options unless you are very comfortable using them.
-
----
-
-### useSecureCookies
-
-- **Default value**: `true` for HTTPS sites / `false` for HTTP sites
-- **Required**: _No_
-
-#### Description
-
-When set to `true` (the default for all site URLs that start with `https://`) then all cookies set by Auth.js will only be accessible from HTTPS URLs.
-
-This option defaults to `false` on URLs that start with `http://` (e.g. `http://localhost:3000`) for developer convenience.
-
-:::note
-Properties on any custom `cookies` that are specified override this option.
-:::
-
-:::warning
-Setting this option to _false_ in production is a security risk and may allow sessions to be hijacked if used in production. It is intended to support development and testing. Using this option is not recommended.
-:::
-
----
-
-### cookies
-
-- **Default value**: `{}`
-- **Required**: _No_
-
-#### Description
-
-Cookies in Auth.js are chunked by default, meaning that once they reach the 4kb limit, we will create a new cookie with the `.{number}` suffix and reassemble the cookies in the correct order when parsing / reading them. This was introduced to avoid size constraints which can occur when users want to store additional data in their sessionToken, for example.
-
-You can override the default cookie names and options for any of the cookies used by Auth.js.
-
-This is an advanced option and using it is not recommended as you may break authentication or introduce security flaws into your application.
-
-You can specify one or more cookies with custom properties, but if you specify custom options for a cookie you must provide all the options for that cookie.
-
-If you use this feature, you will likely want to create conditional behaviour to support setting different cookies policies in development and production builds, as you will be opting out of the built-in dynamic policy.
-
-:::tip
-An example of a use case for this option is to support sharing session tokens across subdomains.
-:::
-
-#### Example
-
-```js
-cookies: {
-  sessionToken: {
-    name: `__Secure-next-auth.session-token`,
-    options: {
-      httpOnly: true,
-      sameSite: 'lax',
-      path: '/',
-      secure: true
-    }
-  },
-  callbackUrl: {
-    name: `__Secure-next-auth.callback-url`,
-    options: {
-      sameSite: 'lax',
-      path: '/',
-      secure: true
-    }
-  },
-  csrfToken: {
-    name: `__Host-next-auth.csrf-token`,
-    options: {
-      httpOnly: true,
-      sameSite: 'lax',
-      path: '/',
-      secure: true
-    }
-  },
-  pkceCodeVerifier: {
-    name: `${cookiePrefix}next-auth.pkce.code_verifier`,
-    options: {
-      httpOnly: true,
-      sameSite: 'lax',
-      path: '/',
-      secure: useSecureCookies,
-      maxAge: 900
-    }
-  },
-  state: {
-    name: `${cookiePrefix}next-auth.state`,
-    options: {
-      httpOnly: true,
-      sameSite: "lax",
-      path: "/",
-      secure: useSecureCookies,
-      maxAge: 900
-    },
-  },
-}
-```
-
-:::warning
-Using a custom cookie policy may introduce security flaws into your application and is intended as an option for advanced users who understand the implications. Using this option is not recommended.
-:::

docs/docs/reference/02-configuration/04-env.md

@@ -1,38 +0,0 @@
----
-title: Environment variables
-sidebar_label: Environment Variables
----
-
-## NEXTAUTH_URL
-
-When deploying to production, set the `NEXTAUTH_URL` environment variable to the canonical URL of your site.
-
-```
-NEXTAUTH_URL=https://example.com
-```
-
-If your Next.js application uses a custom base path, specify the route to the API endpoint in full.
-
-_e.g. `NEXTAUTH_URL=https://example.com/custom-route/api/auth`_
-
-:::note
-Using [System Environment Variables](https://vercel.com/docs/concepts/projects/environment-variables#system-environment-variables) we automatically detect when you deploy to [Vercel](https://vercel.com) so you don't have to define this variable. Make sure **Automatically expose System Environment Variables** is checked in your Project Settings.
-:::
-
----
-
-## NEXTAUTH_SECRET
-
-Used to encrypt the Auth.js JWT, and to hash [email verification tokens](/reference/adapters/models#verification-token). This is the default value for the [`secret`](/reference/configuration/auth-config#secret) option. The `secret` option might be removed in the future in favor of this.
-
-If you are using [Middleware](/reference/nextjs/#prerequisites) this environment variable must be set.
-
----
-
-## NEXTAUTH_URL_INTERNAL
-
-If provided, server-side calls will use this instead of `NEXTAUTH_URL`. Useful in environments when the server doesn't have access to the canonical URL of your site. Defaults to `NEXTAUTH_URL`.
-
-```
-NEXTAUTH_URL_INTERNAL=http://10.240.8.16
-```

docs/docs/reference/02-configuration/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Configuration",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/reference/04-providers/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Providers",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/reference/05-oauth-providers/42.md

@@ -1,38 +0,0 @@
----
-id: 42-school
-title: 42 School
----
-
-:::note
-42 returns a field on `Account` called `created_at` which is a number. See the [docs](https://api.intra.42.fr/apidoc/guides/getting_started#make-basic-requests). Make sure to add this field to your database schema, in case if you are using an [Adapter](/reference/adapters/overview).
-:::
-
-## Documentation
-
-https://api.intra.42.fr/apidoc/guides/web_application_flow
-
-## Configuration
-
-https://profile.intra.42.fr/oauth/applications/new
-
-## Options
-
-The **42 School Provider** comes with a set of default options:
-
-- [42 School Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/42-school.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import FortyTwoProvider from "next-auth/providers/42-school";
-...
-providers: [
-  FortyTwoProvider({
-    clientId: process.env.FORTY_TWO_CLIENT_ID,
-    clientSecret: process.env.FORTY_TWO_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "OAuth Providers",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/reference/05-oauth-providers/apple.md

@@ -1,137 +0,0 @@
----
-id: apple
-title: Apple
----
-
-## Documentation
-
-https://developer.apple.com/sign-in-with-apple/get-started/
-
-## Configuration
-
-https://developer.apple.com/account/resources/identifiers/list/serviceId
-
-## Options
-
-The **Apple Provider** comes with a set of default options:
-
-- [Apple Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/apple.ts)
-
-You can override any of the options to suit your own use case.
-
-### Generating a secret
-
-Apple requires the client secret to be a JWT. To generate one, you can use the following script: https://bal.so/apple-gen-secret.
-
-For more information, see the [Apple docs](https://developer.apple.com/documentation/sign_in_with_apple/generate_and_validate_tokens#3262048)
-
-Then, you can paste the result into your `.env.local` file under `APPLE_SECRET`, so you can refer to it from your code:
-
-```js
-import AppleProvider from "next-auth/providers/apple";
-...
-providers: [
-  AppleProvider({
-    clientId: process.env.APPLE_ID,
-    clientSecret: process.env.APPLE_SECRET
-  })
-]
-...
-```
-
-:::tip
-The TeamID is located on the top right after logging in.
-:::
-
-:::tip
-The KeyID is located after you create the key. Look for it before you download the k8 file.
-:::
-
-## Testing on a development server
-
-:::tip
-Apple requires all sites to run HTTPS (including local development instances).
-:::
-
-:::tip
-Apple doesn't allow you to use localhost in domains or subdomains.
-:::
-
-### Host name resolution
-
-Edit your host file and point your site to `127.0.0.1`.
-
-_Linux/macOS_
-
-```
-sudo echo '127.0.0.1 dev.example.com' >> /etc/hosts
-```
-
-_Windows_ (run PowerShell as administrator)
-
-```ps
-Add-Content -Path C:\Windows\System32\drivers\etc\hosts -Value "127.0.0.1 dev.example.com" -Force
-```
-
-More info: [How to edit my host file?](https://phoenixnap.com/kb/how-to-edit-hosts-file-in-windows-mac-or-linux)
-
-### Create certificate
-
-Create a directory `certificates` and add the certificate files `localhost.key` and `localhost.crt`, which you generate using OpenSSL:
-
-_Linux/macOS_
-
-```bash
-openssl req -x509 -out localhost.crt -keyout localhost.key \
-  -newkey rsa:2048 -nodes -sha256 \
-  -subj "/CN=localhost" -extensions EXT -config <( \
-   printf "[dn]\nCN=localhost\n[req]\ndistinguished_name = dn\n[EXT]\nsubjectAltName=DNS:localhost\nkeyUsage=digitalSignature\nextendedKeyUsage=serverAuth")
-```
-
-_Windows_
-
-The OpenSSL executable is distributed with [Git](https://git-scm.com/download/win) for Windows. Once installed you will find the openssl.exe file in `C:\Program Files\Git\mingw64\bin`, which you can add to the system PATH environment variable if it’s not already done.
-
-Add environment variable `OPENSSL_CONF=C:\Program Files\Git\mingw64\ssl\openssl.cnf`
-
-```cmd
- req -x509 -out localhost.crt -keyout localhost.key \
-  -newkey rsa:2048 -nodes -sha256 \
-  -subj "/CN=localhost"
-```
-
-### Deploy to server
-
-You can create a `server.js` in the root of your project and run it with `node server.js` to test Sign in with Apple integration locally:
-
-```js
-const { createServer } = require("https")
-const { parse } = require("url")
-const next = require("next")
-const fs = require("fs")
-
-const dev = process.env.NODE_ENV !== "production"
-const app = next({ dev })
-const handle = app.getRequestHandler()
-
-const httpsOptions = {
-  key: fs.readFileSync("./certificates/localhost.key"),
-  cert: fs.readFileSync("./certificates/localhost.crt"),
-}
-
-app.prepare().then(() => {
-  createServer(httpsOptions, (req, res) => {
-    const parsedUrl = parse(req.url, true)
-    handle(req, res, parsedUrl)
-  }).listen(3000, (err) => {
-    if (err) throw err
-    console.log("> Ready on https://localhost:3000")
-  })
-})
-```
-
-### Helpful guides
-
-- [How to setup localhost with HTTPS with a Next.js app](https://medium.com/@anMagpie/secure-your-local-development-server-with-https-next-js-81ac6b8b3d68)
-
-- [Guide to configuring Sign in with Apple](https://developer.okta.com/blog/2019/06/04/what-the-heck-is-sign-in-with-apple)

docs/docs/reference/05-oauth-providers/atlassian.md

@@ -1,52 +0,0 @@
----
-id: atlassian
-title: Atlassian
----
-
-## Documentation
-
-https://developer.atlassian.com/cloud/jira/platform/oauth-2-authorization-code-grants-3lo-for-apps/#implementing-oauth-2-0--3lo-
-
-## Options
-
-The **Atlassian Provider** comes with a set of default options:
-
-- [Atlassian Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/atlassian.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import AtlassianProvider from "next-auth/providers/atlassian";
-...
-providers: [
-  AtlassianProvider({
-    clientId: process.env.ATLASSIAN_CLIENT_ID,
-    clientSecret: process.env.ATLASSIAN_CLIENT_SECRET,
-    authorization: {
-      params: {
-        scope: "write:jira-work read:jira-work read:jira-user offline_access read:me"
-      }
-    }
-  })
-]
-...
-```
-
-## Instructions
-
-### Configuration
-
-:::tip
-An app can be created at https://developer.atlassian.com/apps/
-:::
-
-Under "Apis and features" in the side menu, configure the following for "OAuth 2.0 (3LO)":
-
-- Redirect URL
-  - http://localhost:3000/api/auth/callback/atlassian
-
-:::warning
-To enable access to Jira Platform REST API you must enable User Identity API and add `read:me` to your provider scope option.
-:::

docs/docs/reference/05-oauth-providers/auth0.md

@@ -1,39 +0,0 @@
----
-id: auth0
-title: Auth0
----
-
-## Documentation
-
-https://auth0.com/docs/api/authentication#authorize-application
-
-## Configuration
-
-https://manage.auth0.com/dashboard
-
-## Options
-
-The **Auth0 Provider** comes with a set of default options:
-
-- [Auth0 Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/auth0.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import Auth0Provider from "next-auth/providers/auth0";
-...
-providers: [
-  Auth0Provider({
-    clientId: process.env.AUTH0_CLIENT_ID,
-    clientSecret: process.env.AUTH0_CLIENT_SECRET,
-    issuer: process.env.AUTH0_ISSUER
-  })
-]
-...
-```
-
-:::note
-`issuer` should be the fully qualified URL – e.g. `https://dev-s6clz2lv.eu.auth0.com`
-:::

docs/docs/reference/05-oauth-providers/authentik.md

@@ -1,35 +0,0 @@
----
-id: authentik
-title: Authentik
----
-
-## Documentation
-
-https://goauthentik.io/docs/providers/oauth2
-
-## Options
-
-The **Authentik Provider** comes with a set of default options:
-
-- [Authentik Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/authentik.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import AuthentikProvider from "next-auth/providers/authentik";
-...
-providers: [
-  AuthentikProvider({
-    clientId: process.env.AUTHENTIK_ID,
-    clientSecret: process.env.AUTHENTIK_SECRET,
-    issuer: process.env.AUTHENTIK_ISSUER,
-  })
-]
-...
-```
-
-:::note
-`issuer` should include the slug without a trailing slash – e.g., `https://my-authentik-domain.com/application/o/My_Slug`
-:::

docs/docs/reference/05-oauth-providers/azure-ad-b2c.md

@@ -1,117 +0,0 @@
----
-id: azure-ad-b2c
-title: Azure Active Directory B2C
----
-
-:::note
-Azure AD B2C returns the following fields on `Account`:
-
-- `refresh_token_expires_in` (number)
-- `not_before` (number)
-- `id_token_expires_in` (number)
-- `profile_info` (string).
-
-See their [docs](https://docs.microsoft.com/en-us/azure/active-directory-b2c/access-tokens). Remember to add these fields to your database schema, in case if you are using an [Adapter](/reference/adapters/overview).
-:::
-
-## Documentation
-
-https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-auth-code-flow
-
-## Configuration
-
-https://docs.microsoft.com/azure/active-directory-b2c/tutorial-create-tenant
-
-## Options
-
-The **Azure Active Directory Provider** comes with a set of default options:
-
-- [Azure Active Directory Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/azure-ad-b2c.ts)
-
-You can override any of the options to suit your own use case.
-
-## Configuration (Basic)
-
-Basic configuration sets up Azure AD B2C to return an ID Token. This should be done as a prerequisite prior to running through the Advanced configuration.
-
-Step 1: Azure AD B2C Tenant
-https://docs.microsoft.com/en-us/azure/active-directory-b2c/tutorial-create-tenant
-
-Step 2: App Registration
-https://docs.microsoft.com/en-us/azure/active-directory-b2c/tutorial-register-applications
-
-Step 3: User Flow
-https://docs.microsoft.com/en-us/azure/active-directory-b2c/tutorial-create-user-flows
-
-Note: For the step "User attributes and token claims" you might minimally:
-
-- Collect attribute:
-  - Email Address
-  - Display Name
-  - Given Name
-  - Surname
-- Return claim:
-  - Email Addresses
-  - Display Name
-  - Given Name
-  - Surname
-  - Identity Provider
-  - Identity Provider Access Token
-  - User's Object ID
-
-## Example
-
-In `.env.local` create the following entries:
-
-```
-AZURE_AD_B2C_TENANT_NAME=<copy the B2C tenant name here from Step 1>
-AZURE_AD_B2C_CLIENT_ID=<copy Application (client) ID here from Step 2>
-AZURE_AD_B2C_CLIENT_SECRET=<copy generated secret value here from Step 2>
-AZURE_AD_B2C_PRIMARY_USER_FLOW=<copy the name of the signin user flow you created from Step 3>
-```
-
-In `pages/api/auth/[...nextauth].js` find or add the AZURE_AD_B2C entries:
-
-```js
-import AzureADB2CProvider from "next-auth/providers/azure-ad-b2c";
-...
-providers: [
-  AzureADB2CProvider({
-    tenantId: process.env.AZURE_AD_B2C_TENANT_NAME,
-    clientId: process.env.AZURE_AD_B2C_CLIENT_ID,
-    clientSecret: process.env.AZURE_AD_B2C_CLIENT_SECRET,
-    primaryUserFlow: process.env.AZURE_AD_B2C_PRIMARY_USER_FLOW,
-    authorization: { params: { scope: "offline_access openid" } },
-  }),
-]
-...
-```
-
-## Configuration (Advanced)
-
-Advanced configuration sets up Azure AD B2C to return an Authorization Token. This builds on the steps completed in the Basic configuration above.
-
-Step 4: Add a Web API application
-https://docs.microsoft.com/en-us/azure/active-directory-b2c/tutorial-single-page-app-webapi?tabs=app-reg-ga
-
-Note: this is a second app registration (similar to Step 2) but with different setup and configuration.
-
-## Example
-
-Nothing in `.env.local` needs to change here. The only update is in `pages/api/auth/[...nextauth].js` where you will need to add the additional scopes that were created in Step 4 above:
-
-```js
-import AzureADB2CProvider from "next-auth/providers/azure-ad-b2c";
-...
-providers: [
-  AzureADB2CProvider({
-    tenantId: process.env.AZURE_AD_B2C_TENANT_NAME,
-    clientId: process.env.AZURE_AD_B2C_CLIENT_ID,
-    clientSecret: process.env.AZURE_AD_B2C_CLIENT_SECRET,
-    primaryUserFlow: process.env.AZURE_AD_B2C_PRIMARY_USER_FLOW,
-    authorization: { params: { scope: `https://${process.env.AZURE_AD_B2C_TENANT_NAME}.onmicrosoft.com/api/demo.read https://${process.env.AZURE_AD_B2C_TENANT_NAME}.onmicrosoft.com/api/demo.write offline_access openid` } },
-  }),
-]
-...
-
-```

docs/docs/reference/05-oauth-providers/azure-ad.md

@@ -1,59 +0,0 @@
----
-id: azure-ad
-title: Azure Active Directory
----
-
-## Documentation
-
-https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow
-
-## Configuration
-
-https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app
-
-## Example
-
-### To allow specific Active Directory users access:
-
-- In https://portal.azure.com/ search for "Azure Active Directory", and select your organization.
-- Next, go to "App Registration" in the left menu, and create a new one.
-- Pay close attention to "Who can use this application or access this API?"
-  - This allows you to scope access to specific types of user accounts
-  - Only your tenant, all azure tenants, or all azure tenants and public Microsoft accounts (Skype, Xbox, Outlook.com, etc.)
-- When asked for a redirection URL, use `https://yourapplication.com/api/auth/callback/azure-ad` or for development `http://localhost:3000/api/auth/callback/azure-ad`.
-- After your App Registration is created, under "Client Credential" create your Client secret.
-- Now copy your:
-  - Application (client) ID
-  - Directory (tenant) ID
-  - Client secret (value)
-
-In `.env.local` create the following entries:
-
-```
-AZURE_AD_CLIENT_ID=<copy Application (client) ID here>
-AZURE_AD_CLIENT_SECRET=<copy generated client secret value here>
-AZURE_AD_TENANT_ID=<copy the tenant id here>
-```
-
-That will default the tenant to use the `common` authorization endpoint. [For more details see here](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols#endpoints).
-
-:::note
-Azure AD returns the profile picture in an ArrayBuffer, instead of just a URL to the image, so our provider converts it to a base64 encoded image string and returns that instead. See: https://docs.microsoft.com/en-us/graph/api/profilephoto-get?view=graph-rest-1.0#examples. The default image size is 48x48 to avoid [running out of space](https://authjs.dev/concepts/faq#:~:text=What%20are%20the%20disadvantages%20of%20JSON%20Web%20Tokens%3F) in case the session is saved as a JWT.
-:::
-
-In `pages/api/auth/[...nextauth].js` find or add the `AzureAD` entries:
-
-```js
-import AzureADProvider from "next-auth/providers/azure-ad";
-
-...
-providers: [
-  AzureADProvider({
-    clientId: process.env.AZURE_AD_CLIENT_ID,
-    clientSecret: process.env.AZURE_AD_CLIENT_SECRET,
-    tenantId: process.env.AZURE_AD_TENANT_ID,
-  }),
-]
-...
-
-```

docs/docs/reference/05-oauth-providers/battlenet.md

@@ -1,46 +0,0 @@
----
-id: battle.net
-title: Battle.net
----
-
-## Documentation
-
-https://develop.battle.net/documentation/guides/using-oauth
-
-## Configuration
-
-https://develop.battle.net/access/clients
-
-## Options
-
-The **Battle.net Provider** comes with a set of default options:
-
-- [Battle.net Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/battlenet.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import BattleNetProvider from "next-auth/providers/battlenet";
-...
-providers: [
-  BattleNetProvider({
-    clientId: process.env.BATTLENET_CLIENT_ID,
-    clientSecret: process.env.BATTLENET_CLIENT_SECRET,
-    issuer: process.env.BATTLENET_ISSUER
-  })
-]
-...
-```
-
-`issuer` must be one of these values, based on the [available regions](https://develop.battle.net/documentation/guides/regionality-and-apis):
-
-```ts
-type BattleNetIssuer =
-  | "https://www.battlenet.com.cn/oauth"
-  | "https://us.battle.net/oauth"
-  | "https://eu.battle.net/oauth"
-  | "https://kr.battle.net/oauth"
-  | "https://tw.battle.net/oauth"
-```

docs/docs/reference/05-oauth-providers/box.md

@@ -1,34 +0,0 @@
----
-id: box
-title: Box
----
-
-## Documentation
-
-https://developer.box.com/reference/
-
-## Configuration
-
-https://developer.box.com/guides/sso-identities-and-app-users/connect-okta-to-app-users/configure-box/
-
-## Options
-
-The **Box Provider** comes with a set of default options:
-
-- [Box Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/box.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import BoxProvider from "next-auth/providers/box";
-...
-providers: [
-  BoxProvider({
-    clientId: process.env.BOX_CLIENT_ID,
-    clientSecret: process.env.BOX_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/boxyhq-saml.md

@@ -1,58 +0,0 @@
----
-id: boxyhq-saml
-title: BoxyHQ SAML
----
-
-## Documentation
-
-BoxyHQ SAML is an open source service that handles the SAML login flow as an OAuth 2.0 flow, abstracting away all the complexities of the SAML protocol.
-
-You can deploy BoxyHQ SAML as a separate service or embed it into your app using our NPM library. [Check out the documentation for more details](https://boxyhq.com/docs/jackson/deploy)
-
-## Configuration
-
-SAML login requires a configuration for every tenant of yours. One common method is to use the domain for an email address to figure out which tenant they belong to. You can also use a unique tenant ID (string) from your backend for this, typically some kind of account or organization ID.
-
-Check out the [documentation](https://boxyhq.com/docs/jackson/saml-flow#2-saml-config-api) for more details.
-
-## Options
-
-The **BoxyHQ SAML Provider** comes with a set of default options:
-
-- [BoxyHQ Provider options](https://github.com/nextauthjs/next-auth/tree/main/packages/next-auth/src/providers/boxyhq-saml.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```ts
-import BoxyHQSAMLProvider from "next-auth/providers/boxyhq-saml"
-...
-providers: [
-  BoxyHQSAMLProvider({
-    issuer: "http://localhost:5225",
-    clientId: "dummy", // The dummy here is necessary since we'll pass tenant and product custom attributes in the client code
-    clientSecret: "dummy", // The dummy here is necessary since we'll pass tenant and product custom attributes in the client code
-  })
-}
-...
-```
-
-On the client side you'll need to pass additional parameters `tenant` and `product` to the `signIn` function. This will allow BoxyHQL SAML to figure out the right SAML configuration and take your user to the right SAML Identity Provider to sign them in.
-
-```tsx
-import { signIn } from "next-auth/react";
-...
-
-  // Map your users's email to a tenant and product
-  const tenant = email.split("@")[1];
-  const product = 'my_awesome_product';
-...
-  <Button
-    onClick={async (event) => {
-      event.preventDefault();
-
-      signIn("boxyhq-saml", {}, { tenant, product });
-    }}>
-...
-```

docs/docs/reference/05-oauth-providers/bungie.md

@@ -1,137 +0,0 @@
----
-id: bungie
-title: Bungie
----
-
-## Documentation
-
-https://github.com/Bungie-net/api/wiki/OAuth-Documentation
-
-## Configuration
-
-https://www.bungie.net/en/Application
-
-## Options
-
-The **Bungie Provider** comes with a set of default options:
-
-- [Bungie Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/bungie.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import BungieProvider from "next-auth/providers/bungie";
-...
-providers: [
-  BungieProvider({
-    clientId: process.env.BUNGIE_CLIENT_ID,
-    clientSecret: process.env.BUNGIE_SECRET,
-    headers: {
-      "X-API-Key": process.env.BUNGIE_API_KEY
-    }
-  }),
-]
-...
-```
-
-### Configuration
-
-:::tip
-Bungie require all sites to run HTTPS (including local development instances).
-:::
-
-:::tip
-Bungie doesn't allow you to use localhost as the website URL, instead you need to use https://127.0.0.1:3000
-:::
-
-Navigate to https://www.bungie.net/en/Application and fill in the required details:
-
-- Application name
-- Application Status
-- Website
-- OAuth Client Type
-  - Confidential
-- Redirect URL
-  - https://localhost:3000/api/auth/callback/bungie
-- Scope
-  - `Access items like your Bungie.net notifications, memberships, and recent Bungie.Net forum activity.`
-- Origin Header
-
-The following guide may be helpful:
-
-- [How to setup localhost with HTTPS with a Next.js app](https://medium.com/@anMagpie/secure-your-local-development-server-with-https-next-js-81ac6b8b3d68)
-
-### Example server
-
-You will need to edit your host file and point your site at `127.0.0.1`
-
-[How to edit my host file?](https://phoenixnap.com/kb/how-to-edit-hosts-file-in-windows-mac-or-linux)
-
-On Windows (Run Powershell as administrator)
-
-```ps
-Add-Content -Path C:\Windows\System32\drivers\etc\hosts -Value "127.0.0.1`tdev.example.com" -Force
-```
-
-```
-127.0.0.1 dev.example.com
-```
-
-#### Create certificate
-
-Creating a certificate for localhost is easy with openssl. Just put the following command in the terminal. The output will be two files: localhost.key and localhost.crt.
-
-```bash
-openssl req -x509 -out localhost.crt -keyout localhost.key \
-  -newkey rsa:2048 -nodes -sha256 \
-  -subj "/CN=localhost" -extensions EXT -config <( \
-   printf "[dn]\nCN=localhost\n[req]\ndistinguished_name = dn\n[EXT]\nsubjectAltName=DNS:localhost\nkeyUsage=digitalSignature\nextendedKeyUsage=serverAuth")
-```
-
-:::tip
-**Windows**
-
-The OpenSSL executable is distributed with [Git](https://git-scm.com/download/win]9) for Windows.
-Once installed you will find the openssl.exe file in `C:/Program Files/Git/mingw64/bin` which you can add to the system PATH environment variable if it’s not already done.
-
-Add environment variable `OPENSSL_CONF=C:/Program Files/Git/mingw64/ssl/openssl.cnf`
-
-```bash
- req -x509 -out localhost.crt -keyout localhost.key \
-  -newkey rsa:2048 -nodes -sha256 \
-  -subj "/CN=localhost"
-```
-
-:::
-
-Create directory `certificates` and place `localhost.key` and `localhost.crt`
-
-You can create a `server.js` in the root of your project and run it with `node server.js` to test Sign in with Bungie integration locally:
-
-```js
-const { createServer } = require("https")
-const { parse } = require("url")
-const next = require("next")
-const fs = require("fs")
-
-const dev = process.env.NODE_ENV !== "production"
-const app = next({ dev })
-const handle = app.getRequestHandler()
-
-const httpsOptions = {
-  key: fs.readFileSync("./certificates/localhost.key"),
-  cert: fs.readFileSync("./certificates/localhost.crt"),
-}
-
-app.prepare().then(() => {
-  createServer(httpsOptions, (req, res) => {
-    const parsedUrl = parse(req.url, true)
-    handle(req, res, parsedUrl)
-  }).listen(3000, (err) => {
-    if (err) throw err
-    console.log("> Ready on https://localhost:3000")
-  })
-})
-```

docs/docs/reference/05-oauth-providers/cognito.md

@@ -1,49 +0,0 @@
----
-id: cognito
-title: Amazon Cognito
----
-
-## Documentation
-
-https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-userpools-server-contract-reference.html
-
-## Configuration
-
-https://console.aws.amazon.com/cognito/users/
-
-You need to select your AWS region to go the the Cognito dashboard.
-
-## Options
-
-The **Amazon Cognito Provider** comes with a set of default options:
-
-- [Amazon Cognito Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/cognito.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import CognitoProvider from "next-auth/providers/cognito";
-...
-providers: [
-  CognitoProvider({
-    clientId: process.env.COGNITO_CLIENT_ID,
-    clientSecret: process.env.COGNITO_CLIENT_SECRET,
-    issuer: process.env.COGNITO_ISSUER,
-  })
-]
-...
-```
-
-:::tip
-The issuer is a URL, that looks like this: `https://cognito-idp.{region}.amazonaws.com/{PoolId}`
-:::
-
-`PoolId` is from `General Settings` in Cognito, not to be confused with the App Client ID.
-
-:::warning
-Make sure you select all the appropriate client settings or the OAuth flow will not work.
-:::
-
-![cognito](https://user-images.githubusercontent.com/7902980/83951604-cd096e80-a832-11ea-8bd2-c496ec9a16cb.PNG)

docs/docs/reference/05-oauth-providers/coinbase.md

@@ -1,38 +0,0 @@
----
-id: coinbase
-title: Coinbase
----
-
-## Documentation
-
-https://developers.coinbase.com/api/v2
-
-## Configuration
-
-https://www.coinbase.com/settings/api
-
-## Options
-
-The **Coinbase Provider** comes with a set of default options:
-
-- [Coinbase Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/coinbase.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import CoinbaseProvider from "next-auth/providers/coinbase";
-...
-providers: [
-  CoinbaseProvider({
-    clientId: process.env.COINBASE_CLIENT_ID,
-    clientSecret: process.env.COINBASE_CLIENT_SECRET
-  })
-]
-...
-```
-
-:::tip
-This Provider template has a 2 hour access token to it. A refresh token is also returned.
-:::

docs/docs/reference/05-oauth-providers/discord.md

@@ -1,34 +0,0 @@
----
-id: discord
-title: Discord
----
-
-## Documentation
-
-https://discord.com/developers/docs/topics/oauth2
-
-## Configuration
-
-https://discord.com/developers/applications
-
-## Options
-
-The **Discord Provider** comes with a set of default options:
-
-- [Discord Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/discord.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import DiscordProvider from "next-auth/providers/discord";
-...
-providers: [
-  DiscordProvider({
-    clientId: process.env.DISCORD_CLIENT_ID,
-    clientSecret: process.env.DISCORD_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/dropbox.md

@@ -1,34 +0,0 @@
----
-id: dropbox
-title: Dropbox
----
-
-## Documentation
-
-https://developers.dropbox.com/oauth-guide
-
-## Configuration
-
-https://www.dropbox.com/developers/apps
-
-## Options
-
-The **Dropbox Provider** comes with a set of default options:
-
-- [Dropbox Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/dropbox.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import DropboxProvider from "next-auth/providers/dropbox";
-...
-providers: [
-  DropboxProvider({
-    clientId: process.env.DROPBOX_CLIENT_ID,
-    clientSecret: process.env.DROPBOX_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/eveonline.md

@@ -1,51 +0,0 @@
----
-id: eveonline
-title: EVE Online
----
-
-## Documentation
-
-https://developers.eveonline.com/blog/article/sso-to-authenticated-calls
-
-## Configuration
-
-https://developers.eveonline.com/
-
-## Options
-
-The **EVE Online Provider** comes with a set of default options:
-
-- [EVE Online Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/eveonline.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import EVEOnlineProvider from "next-auth/providers/eveonline";
-...
-providers: [
-  EVEOnlineProvider({
-    clientId: process.env.EVE_CLIENT_ID,
-    clientSecret: process.env.EVE_CLIENT_SECRET
-  })
-]
-...
-```
-
-:::tip When creating your application, make sure to select `Authentication Only` as the connection type.
-
-:::tip If using JWT for the session, you can add the `CharacterID` to the JWT token and session. Example:
-
-```js
-...
-options: {
-  callbacks: {
-    session: async ({ session, token }) => {
-      session.user.id = token.id;
-      return session;
-    }
-  }
-}
-...
-```

docs/docs/reference/05-oauth-providers/facebook.md

@@ -1,42 +0,0 @@
----
-id: facebook
-title: Facebook
----
-
-## Documentation
-
-https://developers.facebook.com/docs/facebook-login/manually-build-a-login-flow/
-
-## Configuration
-
-https://developers.facebook.com/apps/
-
-## Options
-
-The **Facebook Provider** comes with a set of default options:
-
-- [Facebook Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/facebook.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import FacebookProvider from "next-auth/providers/facebook";
-...
-providers: [
-  FacebookProvider({
-    clientId: process.env.FACEBOOK_CLIENT_ID,
-    clientSecret: process.env.FACEBOOK_CLIENT_SECRET
-  })
-]
-...
-```
-
-:::tip
-Production applications cannot use localhost URLs to sign in with Facebook. You need to use a dedicated development application in Facebook to use **localhost** callback URLs.
-:::
-
-:::tip
-Email address may not be returned for accounts created on mobile.
-:::

docs/docs/reference/05-oauth-providers/faceit.md

@@ -1,38 +0,0 @@
----
-id: faceit
-title: FACEIT
----
-
-## Documentation
-
-https://cdn.faceit.com/third_party/docs/FACEIT_Connect_3.0.pdf
-
-## Configuration
-
-https://developers.faceit.com/apps
-
-Grant type: `Authorization Code`
-
-Scopes to have basic infos (email, nickname, guid and avatar) : `openid`, `email`, `profile`
-
-## Options
-
-The **FACEIT Provider** comes with a set of default options:
-
-- [FACEIT Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/faceit.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import FaceItProvider from "next-auth/providers/faceit";
-...
-providers: [
-  FaceItProvider({
-    clientId: process.env.FACEIT_CLIENT_ID,
-    clientSecret: process.env.FACEIT_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/foursquare.md

@@ -1,39 +0,0 @@
----
-id: foursquare
-title: Foursquare
----
-
-## Documentation
-
-https://developer.foursquare.com/docs/places-api/authentication/#web-applications
-
-## Configuration
-
-https://developer.foursquare.com/
-
-:::warning
-Foursquare requires an additional `apiVersion` parameter in [`YYYYMMDD` format](https://developer.foursquare.com/docs/places-api/versioning/), which essentially states "I'm prepared for API changes up to this date".
-:::
-
-## Options
-
-The **Foursquare Provider** comes with a set of default options:
-
-- [Foursquare Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/foursquare.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import FourSquareProvider from "next-auth/providers/foursquare";
-...
-providers: [
-  FourSquareProvider({
-    clientId: process.env.FOURSQUARE_CLIENT_ID,
-    clientSecret: process.env.FOURSQUARE_CLIENT_SECRET,
-    apiVersion: "YYYYMMDD"
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/freshbooks.md

@@ -1,34 +0,0 @@
----
-id: freshbooks
-title: Freshbooks
----
-
-## Documentation
-
-https://www.freshbooks.com/api/authenticating-with-oauth-2-0-on-the-new-freshbooks-api
-
-## Configuration
-
-https://my.freshbooks.com/#/developer
-
-## Options
-
-The Freshbooks Provider comes with a set of default options:
-
-https://www.freshbooks.com/api/start
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import FreshbooksProvider from "next-auth/providers/freshbooks";
-...
-providers: [
-  FreshbooksProvider({
-    clientId: process.env.FRESHBOOKS_CLIENT_ID,
-    clientSecret: process.env.FRESHBOOKS_CLIENT_SECRET,
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/fusionauth.md

@@ -1,59 +0,0 @@
----
-id: fusionauth
-title: FusionAuth
----
-
-## Documentation
-
-https://fusionauth.io/docs/v1/tech/oauth/
-
-## Options
-
-The **FusionAuth Provider** comes with a set of default options:
-
-- [FusionAuth Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/fusionauth.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import FusionAuthProvider from "next-auth/providers/fusionauth";
-...
-providers: [
-  FusionAuthProvider({
-    id: "fusionauth",
-    name: "FusionAuth",
-    issuer:  process.env.FUSIONAUTH_ISSUER,
-    clientId: process.env.FUSIONAUTH_CLIENT_ID,
-    clientSecret: process.env.FUSIONAUTH_SECRET,
-    tenantId: process.env.FUSIONAUTH_TENANT_ID // Only required if you're using multi-tenancy
-  }),
-]
-...
-```
-
-:::warning
-If you're using multi-tenancy, you need to pass in the `tenantId` option to apply the proper theme.
-:::
-
-## Instructions
-
-### Configuration
-
-:::tip
-An application can be created at https://your-fusionauth-server-url/admin/application.
-
-For more information, follow the [FusionAuth 5-minute setup guide](https://fusionauth.io/docs/v1/tech/5-minute-setup-guide).
-:::
-
-In the OAuth settings for your application, configure the following.
-
-- Redirect URL
-  - https://localhost:3000/api/auth/callback/fusionauth
-- Enabled grants
-  - Make sure _Authorization Code_ is enabled.
-
-If using JSON Web Tokens, you need to make sure the signing algorithm is RS256, you can create an RS256 key pair by
-going to Settings, Key Master, generate RSA and choosing SHA-256 as algorithm. After that, go to the JWT settings of
-your application and select this key as Access Token signing key and Id Token signing key.

docs/docs/reference/05-oauth-providers/github.md

@@ -1,46 +0,0 @@
----
-id: github
-title: GitHub
----
-
-:::note
-GitHub returns a field on `Account` called `refresh_token_expires_in` which is a number. See their [docs](https://docs.github.com/en/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens#response). Remember to add this field to your database schema, in case if you are using an [Adapter](/reference/adapters/overview).
-:::
-
-## Documentation
-
-https://developer.github.com/apps/building-oauth-apps/authorizing-oauth-apps
-
-## Configuration
-
-https://github.com/settings/apps
-
-## Options
-
-The **GitHub Provider** comes with a set of default options:
-
-- [GitHub Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/github.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import GitHubProvider from "next-auth/providers/github";
-...
-providers: [
-  GitHubProvider({
-    clientId: process.env.GITHUB_ID,
-    clientSecret: process.env.GITHUB_SECRET
-  })
-]
-...
-```
-
-:::warning
-Only allows one callback URL per Client ID / Client Secret.
-:::
-
-:::tip
-Email address is always returned, even if the user doesn't have a public email address on their profile.
-:::

docs/docs/reference/05-oauth-providers/gitlab.md

@@ -1,38 +0,0 @@
----
-id: gitlab
-title: GitLab
----
-
-## Documentation
-
-https://docs.gitlab.com/ee/api/oauth2.html
-
-## Configuration
-
-https://gitlab.com/-/profile/applications
-
-## Options
-
-The **Gitlab Provider** comes with a set of default options:
-
-- [Gitlab Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/gitlab.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import GitlabProvider from "next-auth/providers/gitlab";
-...
-providers: [
-  GitlabProvider({
-    clientId: process.env.GITLAB_CLIENT_ID,
-    clientSecret: process.env.GITLAB_CLIENT_SECRET
-  })
-]
-...
-```
-
-:::tip
-Enable the _"read_user"_ option in scope if you want to save the users email address on sign up.
-:::

docs/docs/reference/05-oauth-providers/google.md

@@ -1,93 +0,0 @@
----
-id: google
-title: Google
----
-
-## Documentation
-
-https://developers.google.com/identity/protocols/oauth2
-
-## Configuration
-
-https://console.developers.google.com/apis/credentials
-
-The "Authorized redirect URIs" used when creating the credentials must include your full domain and end in the callback path. For example;
-
-- For production: `https://{YOUR_DOMAIN}/api/auth/callback/google`
-- For development: `http://localhost:3000/api/auth/callback/google`
-
-## Options
-
-The **Google Provider** comes with a set of default options:
-
-- [Google Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/google.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import GoogleProvider from "next-auth/providers/google";
-...
-providers: [
-  GoogleProvider({
-    clientId: process.env.GOOGLE_CLIENT_ID,
-    clientSecret: process.env.GOOGLE_CLIENT_SECRET
-  })
-]
-...
-```
-
-:::warning
-Google only provides Refresh Token to an application the first time a user signs in.
-
-To force Google to re-issue a Refresh Token, the user needs to remove the application from their account and sign in again:
-https://myaccount.google.com/permissions
-
-Alternatively, you can also pass options in the `params` object of `authorization` which will force the Refresh Token to always be provided on sign in, however this will ask all users to confirm if they wish to grant your application access every time they sign in.
-
-If you need access to the RefreshToken or AccessToken for a Google account and you are not using a database to persist user accounts, this may be something you need to do.
-
-```js
-const options = {
-  ...
-  providers: [
-    GoogleProvider({
-      clientId: process.env.GOOGLE_ID,
-      clientSecret: process.env.GOOGLE_SECRET,
-      authorization: {
-        params: {
-          prompt: "consent",
-          access_type: "offline",
-          response_type: "code"
-        }
-      }
-    })
-  ],
-  ...
-}
-```
-
-:::
-
-:::tip
-Google also returns a `email_verified` boolean property in the OAuth profile.
-
-You can use this property to restrict access to people with verified accounts at a particular domain.
-
-```js
-const options = {
-  ...
-  callbacks: {
-    async signIn({ account, profile }) {
-      if (account.provider === "google") {
-        return profile.email_verified && profile.email.endsWith("@example.com")
-      }
-      return true // Do different verification for other providers that don't have `email_verified`
-    },
-  }
-  ...
-}
-```
-
-:::

docs/docs/reference/05-oauth-providers/identity-server4.md

@@ -1,61 +0,0 @@
----
-id: identity-server4
-title: IdentityServer4
----
-
-:::warning
-[IdentityServer4 is discontinued](https://identityserver4.readthedocs.io/en/latest/#:~:text=until%20November%202022.) and only releases security updates until November 2022. You should consider an alternative provider.
-:::
-
-## Documentation
-
-https://identityserver4.readthedocs.io/en/latest/
-
-## Options
-
-The **IdentityServer4 Provider** comes with a set of default options:
-
-- [IdentityServer4 Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/identity-server4.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import IdentityServer4Provider from "next-auth/providers/identity-server4";
-...
-providers: [
-  IdentityServer4Provider({
-    id: "identity-server4",
-    name: "IdentityServer4",
-    issuer:  process.env.IdentityServer4_Issuer,
-    clientId: process.env.IdentityServer4_CLIENT_ID,
-    clientSecret: process.env.IdentityServer4_CLIENT_SECRET
-  })
-]
-...
-```
-
-## Demo IdentityServer
-
-The configuration below is for the demo server at https://demo.identityserver.io/
-
-If you want to try it out, you can copy and paste the configuration below.
-
-You can sign in to the demo service with either <b>bob/bob</b> or <b>alice/alice</b>.
-
-```js
-import IdentityServer4Provider from `next-auth/providers/identity-server4`
-...
-providers: [
-  IdentityServer4Provider({
-    id: "demo-identity-server",
-    name: "Demo IdentityServer4",
-    authorization: { params: { scope: "openid profile email api offline_access" } },
-    issuer:  "https://demo.identityserver.io/",
-    clientId: "interactive.confidential",
-    clientSecret: "secret",
-  })
-}
-...
-```

docs/docs/reference/05-oauth-providers/instagram.md

@@ -1,50 +0,0 @@
----
-id: instagram
-title: Instagram
----
-
-## Documentation
-
-https://developers.facebook.com/docs/instagram-basic-display-api/getting-started
-
-## Configuration
-
-https://developers.facebook.com/apps/
-
-## Options
-
-The **Instagram Provider** comes with a set of default options:
-
-- [Instagram Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/instagram.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```jsx
-// pages/api/auth/[...nextauth].js
-import InstagramProvider from "next-auth/providers/instagram";
-...
-providers: [
-  InstagramProvider({
-    clientId: process.env.INSTAGRAM_CLIENT_ID,
-    clientSecret: process.env.INSTAGRAM_CLIENT_SECRET
-  })
-]
-...
-// pages/index.jsx
-import { signIn } from "next-auth/react"
-...
-<button onClick={() => signIn("instagram")}>
-  Sign in
-</button>
-...
-```
-
-:::warning
-Email address is not returned by the Instagram API.
-:::
-
-:::tip
-Instagram display app required callback URL to be configured in your Facebook app and Facebook required you to use **https** even for localhost! In order to do that, you either need to [add an SSL to your localhost](https://www.freecodecamp.org/news/how-to-get-https-working-on-your-local-development-environment-in-5-minutes-7af615770eec/) or use a proxy such as [ngrok](https://ngrok.com/docs).
-:::

docs/docs/reference/05-oauth-providers/kakao.md

@@ -1,40 +0,0 @@
----
-id: kakao
-title: Kakao
----
-
-## Documentation
-
-https://developers.kakao.com/product/kakaoLogin
-
-## Configuration
-
-https://developers.kakao.com/docs/latest/en/kakaologin/common
-
-## Options
-
-The **Kakao Provider** comes with a set of default options:
-
-- [Kakao Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/kakao.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import KakaoProvider from "next-auth/providers/kakao";
-...
-providers: [
-  KakaoProvider({
-    clientId: process.env.KAKAO_CLIENT_ID,
-    clientSecret: process.env.KAKAO_CLIENT_SECRET
-  })
-]
-...
-```
-
-## Instructions
-
-### Configuration
-
-Create a provider and a Kakao application at `https://developers.kakao.com/console/app`. In the settings of the app under Kakao Login, activate web app, change consent items and configure callback URL.

docs/docs/reference/05-oauth-providers/keycloak.md

@@ -1,41 +0,0 @@
----
-id: keycloak
-title: Keycloak
----
-
-## Documentation
-
-https://www.keycloak.org/docs/latest/server_admin/#_oidc_clients
-
-## Configuration
-
-:::tip
-Create an openid-connect client in Keycloak with "confidential" as the "Access Type".
-:::
-
-## Options
-
-The **Keycloak Provider** comes with a set of default options:
-
-- [Keycloak Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/keycloak.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import KeycloakProvider from "next-auth/providers/keycloak";
-...
-providers: [
-  KeycloakProvider({
-    clientId: process.env.KEYCLOAK_ID,
-    clientSecret: process.env.KEYCLOAK_SECRET,
-    issuer: process.env.KEYCLOAK_ISSUER,
-  })
-]
-...
-```
-
-:::note
-`issuer` should include the realm – e.g. `https://my-keycloak-domain.com/realms/My_Realm`
-:::

docs/docs/reference/05-oauth-providers/line.md

@@ -1,47 +0,0 @@
----
-id: line
-title: LINE
----
-
-## Documentation
-
-https://developers.line.biz/en/docs/line-login/integrate-line-login/
-
-## Configuration
-
-https://developers.line.biz/console/
-
-## Options
-
-The **Line Provider** comes with a set of default options:
-
-- [Line Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/line.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import LineProvider from "next-auth/providers/line";
-...
-providers: [
-  LineProvider({
-    clientId: process.env.LINE_CLIENT_ID,
-    clientSecret: process.env.LINE_CLIENT_SECRET
-  })
-]
-...
-```
-
-## Instructions
-
-### Configuration
-
-Create a provider and a LINE login channel at `https://developers.line.biz/console/`. In the settings of the channel under LINE Login, activate web app and configure the following:
-
-- Callback URL
-  - http://localhost:3000/api/auth/callback/line
-
-:::tip
-To retrieve email address, you need to apply for Email address permission. Open [Line Developer Console](https://developers.line.biz/console/), go to your Login Channel. Scroll down bottom to find **OpenID Connect** -> **Email address permission**. Click **Apply** and follow the instruction.
-:::

docs/docs/reference/05-oauth-providers/linkedin.md

@@ -1,38 +0,0 @@
----
-id: linkedin
-title: LinkedIn
----
-
-## Documentation
-
-https://docs.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow
-
-## Configuration
-
-https://www.linkedin.com/developers/apps/
-
-From the Auth tab get the client ID and client secret. On the same tab, add redirect URLs such as http://localhost:3000/api/auth/callback/linkedin so LinkedIn can correctly redirect back to your application. Finally, head over to the Products tab and enable the "Sign In with LinkedIn" product. The LinkedIn team will review and approve your request before you can test it out.
-
-![image](https://user-images.githubusercontent.com/330396/114429603-68195600-9b72-11eb-8311-62e58383c42b.png)
-
-## Options
-
-The **LinkedIn Provider** comes with a set of default options:
-
-- [LinkedIn Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/linkedin.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import LinkedInProvider from "next-auth/providers/linkedin";
-...
-providers: [
-  LinkedInProvider({
-    clientId: process.env.LINKEDIN_CLIENT_ID,
-    clientSecret: process.env.LINKEDIN_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/mailchimp.md

@@ -1,34 +0,0 @@
----
-id: mailchimp
-title: Mailchimp
----
-
-## Documentation
-
-https://mailchimp.com/developer/marketing/guides/access-user-data-oauth-2/
-
-## Configuration
-
-https://admin.mailchimp.com/account/oauth2/client/
-
-## Options
-
-The **Mailchimp Provider** comes with a set of default options:
-
-- [Mailchimp Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/mailchimp.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import MailchimpProvider from "next-auth/providers/mailchimp";
-...
-providers: [
-  MailchimpProvider({
-    clientId: process.env.MAILCHIMP_CLIENT_ID,
-    clientSecret: process.env.MAILCHIMP_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/mailru.md

@@ -1,34 +0,0 @@
----
-id: mailru
-title: Mail.ru
----
-
-## Documentation
-
-https://o2.mail.ru/docs
-
-## Configuration
-
-https://o2.mail.ru/app/
-
-## Options
-
-The **Mail.ru Provider** comes with a set of default options:
-
-- [Mail.ru Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/mailru.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import MailRuProvider from "next-auth/providers/mailru";
-...
-providers: [
-  MailRuProvider({
-    clientId: process.env.MAILRU_CLIENT_ID,
-    clientSecret: process.env.MAILRU_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/mattermost.md

@@ -1,36 +0,0 @@
----
-id: mattermost
-title: Mattermost
----
-
-## Documentation
-
-https://developers.mattermost.com/integrate/apps/authentication/oauth2
-
-## Configuration
-
-http://my-cool-server.cloud.mattermost.com/mycoolteam/integrations/oauth2-apps
-
-## Options
-
-The **Mattermost provider** comes with a set of default options:
-
-- [Mattermost Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/providers/mattermost.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```ts
-import Mattermost from "@auth/core/providers/mattermost";
-...
-providers: [
-  Mattermost({
-    // The base url of your Mattermost instance. e.g https://my-cool-server.cloud.mattermost.com
-    clientId: env.MATTERMOST_ID,
-    clientSecret: env.MATTERMOST_SECRET,
-    issuer: env.MATTERMOST_ISSUER,
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/medium.md

@@ -1,38 +0,0 @@
----
-id: medium
-title: Medium
----
-
-## Documentation
-
-https://github.com/Medium/medium-api-docs
-
-## Configuration
-
-https://medium.com/me/applications
-
-## Options
-
-The **Medium Provider** comes with a set of default options:
-
-- [Medium Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/medium.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import MediumProvider from "next-auth/providers/medium";
-...
-providers: [
-  MediumProvider({
-    clientId: process.env.MEDIUM_CLIENT_ID,
-    clientSecret: process.env.MEDIUM_CLIENT_SECRET
-  })
-}
-...
-```
-
-:::warning
-Email address is not returned by the Medium API.
-:::

docs/docs/reference/05-oauth-providers/naver.md

@@ -1,34 +0,0 @@
----
-id: naver
-title: Naver
----
-
-## Documentation
-
-https://developers.naver.com/docs/login/overview/overview.md
-
-## Configuration
-
-https://developers.naver.com/docs/login/api/api.md
-
-## Options
-
-The **Naver Provider** comes with a set of default options:
-
-- [Naver Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/naver.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import NaverProvider from "next-auth/providers/naver";
-...
-providers: [
-  NaverProvider({
-    clientId: process.env.NAVER_CLIENT_ID,
-    clientSecret: process.env.NAVER_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/netlify.md

@@ -1,34 +0,0 @@
----
-id: netlify
-title: Netlify
----
-
-## Documentation
-
-https://www.netlify.com/blog/2016/10/10/integrating-with-netlify-oauth2/
-
-## Configuration
-
-https://github.com/netlify/netlify-oauth-example
-
-## Options
-
-The **Netlify Provider** comes with a set of default options:
-
-- [Netlify Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/netlify.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import NetlifyProvider from "next-auth/providers/netlify";
-...
-providers: [
-  NetlifyProvider({
-    clientId: process.env.NETLIFY_CLIENT_ID,
-    clientSecret: process.env.NETLIFY_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/okta.md

@@ -1,31 +0,0 @@
----
-id: okta
-title: Okta
----
-
-## Documentation
-
-https://developer.okta.com/docs/reference/api/oidc
-
-## Options
-
-The **Okta Provider** comes with a set of default options:
-
-- [Okta Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/okta.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import OktaProvider from "next-auth/providers/okta";
-...
-providers: [
-  OktaProvider({
-    clientId: process.env.OKTA_CLIENT_ID,
-    clientSecret: process.env.OKTA_CLIENT_SECRET,
-    issuer: process.env.OKTA_ISSUER
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/onelogin.md

@@ -1,35 +0,0 @@
----
-id: onelogin
-title: OneLogin
----
-
-## Documentation
-
-https://developers.onelogin.com/openid-connect
-
-## Configuration
-
-https://developers.onelogin.com/openid-connect/connect-to-onelogin
-
-## Options
-
-The **OneLogin Provider** comes with a set of default options:
-
-- [OneLogin Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/onelogin.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import OneLoginProvider from "next-auth/providers/onelogin";
-...
-providers: [
-  OneLoginProvider({
-    clientId: process.env.ONELOGIN_CLIENT_ID,
-    clientSecret: process.env.ONELOGIN_CLIENT_SECRET,
-    issuer: process.env.ONELOGIN_ISSUER
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/osso.md

@@ -1,47 +0,0 @@
----
-id: osso
-title: Osso
----
-
-## Documentation
-
-Osso is an open source service that handles SAML authentication against Identity Providers, normalizes profiles, and makes those profiles available to you in an OAuth 2.0 code grant flow.
-
-If you don't yet have an Osso instance, you can use [Osso's Demo App](https://demo.ossoapp.com) for your testing purposes. For documentation on deploying an Osso instance, see https://ossoapp.com/docs/deploy/overview/
-
-## Configuration
-
-You can configure your OAuth Clients on your Osso Admin UI, i.e. https://demo.ossoapp.com/admin/config - you'll need to get a Client ID and Secret and allow-list your redirect URIs.
-
-[SAML SSO differs a bit from OAuth](https://ossoapp.com/blog/saml-vs-oauth) - for every tenant who wants to sign in to your application using SAML, you and your customer need to perform a multi-step configuration in Osso's Admin UI and the admin dashboard of the tenant's Identity Provider. Osso provides documentation for providers like Okta and OneLogin, cloud-based IDPs who also offer a developer account that's useful for testing. Osso also provides a [Mock IDP](https://idp.ossoapp.com) that you can use for testing without needing to sign up for an Identity Provider service.
-
-See Osso's complete configuration and testing documentation at https://ossoapp.com/docs/configure/overview
-
-## Options
-
-The **Osso Provider** comes with a set of default options:
-
-- [Osso Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/osso.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-A full example application is available at https://github.com/enterprise-oss/osso-next-auth-example and https://nextjs-demo.ossoapp.com
-
-```js
-import OssoProvider from "next-auth/providers/osso";
-...
-providers: [
-  OssoProvider({
-    clientId: process.env.OSSO_CLIENT_ID,
-    clientSecret: process.env.OSSO_CLIENT_SECRET,
-    issuer: process.env.OSSO_ISSUER
-  })
-}
-...
-```
-
-:::note
-`issuer` should be the fully qualified domain – e.g. `demo.ossoapp.com`
-:::

docs/docs/reference/05-oauth-providers/osu.md

@@ -1,38 +0,0 @@
----
-id: osu
-title: Osu!
----
-
-## Documentation
-
-https://osu.ppy.sh/docs/index.html#authentication
-
-## Configuration
-
-https://osu.ppy.sh/home/account/edit#new-oauth-application
-
-## Options
-
-The **Osu Provider** comes with a set of default options:
-
-- [Osu Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/osu.ts)
-
-You can override any of the options to suit your own use case.
-
-:::note
-Osu! does **not** provide a user email!
-:::
-
-## Example
-
-```js
-import OsuProvider from "next-auth/providers/osu";
-...
-providers: [
-  OsuProvider({
-    clientId: process.env.OSU_CLIENT_ID,
-    clientSecret: process.env.OSU_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/patreon.md

@@ -1,40 +0,0 @@
----
-id: patreon
-title: Patreon
----
-
-## Documentation
-
-https://docs.patreon.com/#apiv2-oauth
-
-## Configuration
-
-:::tip
-Create a API v2 client on [Patreon Platform](https://www.patreon.com/portal/registration/register-clients)
-:::
-
-## Options
-
-The **Patreon Provider** comes with a set of default options:
-
-- [Patreon Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/patreon.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import PatreonProvider from "next-auth/providers/patreon";
-...
-providers: [
-    PatreonProvider({
-      clientId: process.env.PATREON_ID,
-      clientSecret: process.env.PATREON_SECRET,
-    })
-]
-...
-```
-
-:::note
-Make sure you use the scopes defined in [ApiV2](https://docs.patreon.com/#scopes)
-:::

docs/docs/reference/05-oauth-providers/pipedrive.md

@@ -1,30 +0,0 @@
----
-id: pipedrive
-title: Pipedrive
----
-
-## Documentation
-
-https://pipedrive.readme.io/docs/marketplace-oauth-authorization
-
-## Options
-
-The **Pipedrive Provider** comes with a set of default options:
-
-- [Pipedrive Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/pipedrive.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import PipedriveProvider from "next-auth/providers/pipedrive";
-...
-providers: [
-  PipedriveProvider({
-    clientId: process.env.PIPEDRIVE_CLIENT_ID,
-    clientSecret: process.env.PIPEDRIVE_CLIENT_SECRET,
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/reddit.md

@@ -1,73 +0,0 @@
----
-id: reddit
-title: Reddit
----
-
-## Documentation
-
-https://www.reddit.com/dev/api/
-
-## Configuration
-
-https://www.reddit.com/prefs/apps/
-
-## Options
-
-The **Reddit Provider** comes with a set of default options:
-
-- [Reddit Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/reddit.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import RedditProvider from "next-auth/providers/reddit";
-...
-providers: [
-  RedditProvider({
-    clientId: process.env.REDDIT_CLIENT_ID,
-    clientSecret: process.env.REDDIT_CLIENT_SECRET
-  })
-]
-...
-```
-
-:::warning
-Reddit requires authorization every time you go through their page.
-:::
-
-:::warning
-Only allows one callback URL per Client ID / Client Secret.
-:::
-
-:::tip
-This Provider template only has a one hour access token to it and only has the "identity" scope. If you want to get a refresh token as well you must follow this:
-
-```js
-providers: [
-  {
-    id: "reddit",
-    name: "Reddit",
-    clientId: process.env.REDDIT_CLIENT_ID,
-    clientSecret: process.env.REDDIT_CLIENT_SECRET,
-    scope: "identity mysubreddits read", //Check Reddit API Documentation for more. The identity scope is required.
-    type: "oauth",
-    version: "2.0",
-    params: { grant_type: "authorization_code" },
-    accessTokenUrl: " https://www.reddit.com/api/v1/access_token",
-    authorizationUrl:
-      "https://www.reddit.com/api/v1/authorize?response_type=code&duration=permanent",
-    profileUrl: "https://oauth.reddit.com/api/v1/me",
-    profile: (profile) => {
-      return {
-        id: profile.id,
-        name: profile.name,
-        email: null,
-      }
-    },
-  },
-]
-```
-
-:::

docs/docs/reference/05-oauth-providers/salesforce.md

@@ -1,30 +0,0 @@
----
-id: salesforce
-title: Salesforce
----
-
-## Documentation
-
-https://help.salesforce.com/articleView?id=remoteaccess_authenticate.htm&type=5
-
-## Options
-
-The **Salesforce Provider** comes with a set of default options:
-
-- [Salesforce Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/salesforce.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import SalesforceProvider from "next-auth/providers/salesforce";
-...
-providers: [
-  SalesforceProvider({
-    clientId: process.env.SALESFORCE_CLIENT_ID,
-    clientSecret: process.env.SALESFORCE_CLIENT_SECRET,
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/slack.md

@@ -1,41 +0,0 @@
----
-id: slack
-title: Slack
----
-
-## Documentation
-
-https://api.slack.com/authentication
-https://api.slack.com/docs/sign-in-with-slack
-
-## Configuration
-
-https://api.slack.com/apps
-
-:::warning
-Slack requires that the redirect URL of your app uses `https`, even for local development. An easy workaround for this is using a service like [`ngrok`](https://ngrok.com) that creates a secure tunnel to your app, using `https`. Remember to set the url as `NEXTAUTH_URL` as well.
-:::
-
-![](https://i.imgur.com/ydYKTLD.png)
-
-## Options
-
-The **Slack Provider** comes with a set of default options:
-
-- [Slack Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/slack.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import SlackProvider from "next-auth/providers/slack";
-...
-providers: [
-  SlackProvider({
-    clientId: process.env.SLACK_CLIENT_ID,
-    clientSecret: process.env.SLACK_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/spotify.md

@@ -1,34 +0,0 @@
----
-id: spotify
-title: Spotify
----
-
-## Documentation
-
-https://developer.spotify.com/documentation/general/guides/authorization-guide
-
-## Configuration
-
-https://developer.spotify.com/dashboard/applications
-
-## Options
-
-The **Spotify Provider** comes with a set of default options:
-
-- [Spotify Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/spotify.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import SpotifyProvider from "next-auth/providers/spotify";
-...
-providers: [
-  SpotifyProvider({
-    clientId: process.env.SPOTIFY_CLIENT_ID,
-    clientSecret: process.env.SPOTIFY_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/strava.md

@@ -1,30 +0,0 @@
----
-id: strava
-title: Strava
----
-
-## Documentation
-
-http://developers.strava.com/docs/reference/
-
-## Options
-
-The **Strava Provider** comes with a set of default options:
-
-- [Strava Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/strava.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import StravaProvider from "next-auth/providers/strava";
-...
-providers: [
-  StravaProvider({
-    clientId: process.env.STRAVA_CLIENT_ID,
-    clientSecret: process.env.STRAVA_CLIENT_SECRET,
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/todoist.md

@@ -1,35 +0,0 @@
----
-id: todoist
-title: Todoist
----
-
-## Documentation
-
-https://developer.todoist.com/guides/#oauth
-
-## Configuration
-
-https://developer.todoist.com/appconsole.html
-
-## Options
-
-The **Todoist Provider** comes with a set of default options:
-
-- [Todoist Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/todoist.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import TodoistProvider from "next-auth/providers/todoist";
-
-...
-providers: [
-  TodoistProvider({
-    clientId: process.env.TODOIST_ID,
-    clientSecret: process.env.TODOIST_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/trakt.md

@@ -1,41 +0,0 @@
----
-id: trakt
-title: Trakt
----
-
-## Documentation
-
-https://trakt.docs.apiary.io/#reference/authentication-oauth
-
-## Configuration
-
-If you're using the api in production by calling [api.trakt.tv](https://api.trakt.tv). Follow the example below. If you wish to develop on Trakt's sandbox environment by calling [api-staging.trakt.tv](https://api-staging.trakt.tv). Use the default options with the changed the URLs.
-
-Start by creating an OAuth app on Trakt for [production](https://trakt.tv/oauth/applications/new) or [development](https://staging.trakt.tv/oauth/applications/new). Then set the Client ID and Client Secret as `TRAKT_ID` and `TRAKT_SECRET` in `.env`.
-
-## Options
-
-The **Trakt Provider** comes with a set of default options:
-
-- [Trakt Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/trakt.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-providers: [
-  TraktProvider({
-    clientId: process.env.TRAKT_ID,
-    clientSecret: process.env.TRAKT_SECRET,
-  }),
-]
-```
-
-:::warning
-Trakt does not allow hotlinking images. Even the authenticated user's profile picture.
-:::
-
-:::warning
-Trakt does not supply the authenticated user's email.
-:::

docs/docs/reference/05-oauth-providers/twitch.md

@@ -1,36 +0,0 @@
----
-id: twitch
-title: Twitch
----
-
-## Documentation
-
-https://dev.twitch.tv/docs/authentication
-
-## Configuration
-
-https://dev.twitch.tv/console/apps
-
-Add the following redirect URL into the console `http://<your-next-app-url>/api/auth/callback/twitch`
-
-## Options
-
-The **Twitch Provider** comes with a set of default options:
-
-- [Twitch Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/twitch.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import TwitchProvider from "next-auth/providers/twitch";
-...
-providers: [
-  TwitchProvider({
-    clientId: process.env.TWITCH_CLIENT_ID,
-    clientSecret: process.env.TWITCH_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/twitter.md

@@ -1,62 +0,0 @@
----
-id: twitter
-title: Twitter
----
-
-:::note
-Twitter is currently the only built-in provider using the OAuth 1.0 spec. This means that you won't receive an `access_token` or `refresh_token`, but an `oauth_token` and `oauth_token_secret` respectively. Remember to add these to your database schema, in case if you are using an [Adapter](/reference/adapters/overview).
-:::
-
-## Documentation
-
-https://developer.twitter.com
-
-## Configuration
-
-https://developer.twitter.com/en/apps
-
-## Options
-
-The **Twitter Provider** comes with a set of default options:
-
-- [Twitter Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/twitter.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import TwitterProvider from "next-auth/providers/twitter";
-...
-providers: [
-  TwitterProvider({
-    clientId: process.env.TWITTER_CLIENT_ID,
-    clientSecret: process.env.TWITTER_CLIENT_SECRET
-  })
-]
-...
-```
-
-:::tip
-You must enable the _"Request email address from users"_ option in your app permissions if you want to obtain the users email address.
-:::
-
-![twitter](https://user-images.githubusercontent.com/55143799/168702338-a95912a7-b689-4680-aa2c-6306fe3c2ec7.jpeg)
-
-## OAuth 2.0
-
-Twitter supports OAuth 2, which is currently opt-in. To enable it, simply add `version: "2.0"` to your Provider configuration:
-
-```js
-TwitterProvider({
-  clientId: process.env.TWITTER_ID,
-  clientSecret: process.env.TWITTER_SECRET,
-  version: "2.0", // opt-in to Twitter OAuth 2.0
-})
-```
-
-Keep in mind that although this change is easy, it changes how and with which of [Twitter APIs](https://developer.twitter.com/en/docs/api-reference-index) you can interact with. Read the official [Twitter OAuth 2 documentation](https://developer.twitter.com/en/docs/authentication/oauth-2-0) for more details.
-
-:::note
-Email is currently not supported by Twitter OAuth 2.0.
-:::

docs/docs/reference/05-oauth-providers/united-effects.md

@@ -1,43 +0,0 @@
----
-id: united-effects
-title: United Effects
----
-
-## Documentation
-
-https://docs.unitedeffects.com/integrations/nextauthjs
-
-## Configuration
-
-https://core.unitedeffects.com
-
-## Options
-
-The **United Effects Provider** comes with a set of default options:
-
-- [United Effects Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/united-effects.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import UnitedEffectsProvider from "next-auth/providers/united-effects";
-...
-providers: [
-  UnitedEffectsProvider({
-    clientId: process.env.UNITED_EFFECTS_CLIENT_ID,
-    clientSecret: process.env.UNITED_EFFECTS_CLIENT_SECRET,
-    issuer: process.env.UNITED_EFFECTS_ISSUER
-  })
-]
-...
-```
-
-:::note
-`issuer` should be the fully qualified URL including your Auth Group ID – e.g. `https://auth.unitedeffects.com/YQpbQV5dbW-224dCovz-3`
-:::
-
-:::warning
-The United Effects API does not return the user name or image by design, so this provider will return null for both. United Effects prioritizes user personal information security above all and has built a secured profile access request system separate from the provider API.
-:::

docs/docs/reference/05-oauth-providers/vk.md

@@ -1,57 +0,0 @@
----
-id: vk
-title: VK
----
-
-## Documentation
-
-https://vk.com/dev/first_guide
-
-## Configuration
-
-https://vk.com/apps?act=manage
-
-## Options
-
-The **VK Provider** comes with a set of default options:
-
-- [VK Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/vk.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import VkProvider from "next-auth/providers/vk";
-...
-providers: [
-  VkProvider({
-    clientId: process.env.VK_CLIENT_ID,
-    clientSecret: process.env.VK_CLIENT_SECRET
-  })
-]
-...
-```
-
-:::note
-By default the provider uses `5.126` version of the API. See https://vk.com/dev/versions for more info.
-:::
-
-If you want to use a different version, you can pass it to provider's options object:
-
-```js
-// pages/api/auth/[...nextauth].js
-
-const apiVersion = "5.126"
-...
-providers: [
-  VkProvider({
-    accessTokenUrl: `https://oauth.vk.com/access_token?v=${apiVersion}`,
-    requestTokenUrl: `https://oauth.vk.com/access_token?v=${apiVersion}`,
-    authorizationUrl:
-      `https://oauth.vk.com/authorize?response_type=code&v=${apiVersion}`,
-    profileUrl: `https://api.vk.com/method/users.get?fields=photo_100&v=${apiVersion}`,
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/wordpress.md

@@ -1,38 +0,0 @@
----
-id: wordpress
-title: WordPress.com
----
-
-## Documentation
-
-https://developer.wordpress.com/docs/oauth2/
-
-## Configuration
-
-https://developer.wordpress.com/apps/
-
-## Options
-
-The **Wordpress Provider** comes with a set of default options:
-
-- [Wordpress Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/wordpress.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import WordpressProvider from "next-auth/providers/wordpress";
-...
-providers: [
-  WordpressProvider({
-    clientId: process.env.WORDPRESS_CLIENT_ID,
-    clientSecret: process.env.WORDPRESS_CLIENT_SECRET
-  })
-}
-...
-```
-
-:::tip
-Register your application to obtain Client ID and Client Secret at https://developer.wordpress.com/apps/ Select Type as Web and set Redirect URL to `http://example.com/api/auth/callback/wordpress` where example.com is your site domain.
-:::

docs/docs/reference/05-oauth-providers/workos.md

@@ -1,103 +0,0 @@
----
-id: workos
-title: WorkOS
----
-
-## Documentation
-
-https://workos.com/docs/sso/guide
-
-## Configuration
-
-https://dashboard.workos.com
-
-## Options
-
-The **WorkOS Provider** comes with a set of default options:
-
-- [WorkOS Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/workos.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import WorkOSProvider from "next-auth/providers/workos";
-...
-providers: [
-  WorkOSProvider({
-    clientId: process.env.WORKOS_CLIENT_ID,
-    clientSecret: process.env.WORKOS_API_KEY,
-  }),
-],
-...
-```
-
-WorkOS is not an identity provider itself, but, rather, a bridge to multiple single sign-on (SSO) providers. As a result, we need to make some additional changes to authenticate users using WorkOS.
-
-In order to sign a user in using WorkOS, we need to specify which WorkOS Connection to use. A common way to do this is to collect the user's email address and extract the domain.
-
-This can be done using a custom login page.
-
-To add a custom login page, you can use the `pages` option:
-
-```javascript title="pages/api/auth/[...nextauth].js"
-...
-  pages: {
-    signIn: "/auth/signin",
-  }
-```
-
-We can then add a custom login page that displays an input where the user can enter their email address. We then extract the domain from the user's email address and pass it to the `authorizationParams` parameter on the `signIn` function:
-
-```jsx title="pages/auth/signin.js"
-import { useState } from "react"
-import { getProviders, signIn } from "next-auth/react"
-
-export default function SignIn({ providers }) {
-  const [email, setEmail] = useState("")
-
-  return (
-    <>
-      {Object.values(providers).map((provider) => {
-        if (provider.id === "workos") {
-          return (
-            <div key={provider.id}>
-              <input
-                type="email"
-                value={email}
-                placeholder="Email"
-                onChange={(event) => setEmail(event.target.value)}
-              />
-              <button
-                onClick={() =>
-                  signIn(provider.id, undefined, {
-                    domain: email.split("@")[1],
-                  })
-                }
-              >
-                Sign in with SSO
-              </button>
-            </div>
-          )
-        }
-
-        return (
-          <div key={provider.id}>
-            <button onClick={() => signIn(provider.id)}>
-              Sign in with {provider.name}
-            </button>
-          </div>
-        )
-      })}
-    </>
-  )
-}
-
-export async function getServerSideProps(context) {
-  const providers = await getProviders()
-  return {
-    props: { providers },
-  }
-}
-```

docs/docs/reference/05-oauth-providers/yandex.md

@@ -1,34 +0,0 @@
----
-id: yandex
-title: Yandex
----
-
-## Documentation
-
-https://tech.yandex.com/oauth/doc/dg/concepts/about-docpage/
-
-## Configuration
-
-https://oauth.yandex.com/client/new
-
-## Options
-
-The **Yandex Provider** comes with a set of default options:
-
-- [Yandex Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/yandex.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import YandexProvider from "next-auth/providers/yandex";
-...
-providers: [
-  YandexProvider({
-    clientId: process.env.YANDEX_CLIENT_ID,
-    clientSecret: process.env.YANDEX_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/zoho.md

@@ -1,34 +0,0 @@
----
-id: zoho
-title: Zoho
----
-
-## Documentation
-
-https://www.zoho.com/accounts/protocol/oauth/web-server-applications.html
-
-## Configuration
-
-https://api-console.zoho.com/
-
-## Options
-
-The **Zoho Provider** comes with a set of default options:
-
-- [Zoho Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/zoho.js)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import ZohoProvider from "next-auth/providers/zoho";
-...
-providers: [
-  ZohoProvider({
-    clientId: process.env.ZOHO_CLIENT_ID,
-    clientSecret: process.env.ZOHO_CLIENT_SECRET
-  })
-]
-...
-```

docs/docs/reference/05-oauth-providers/zoom.md

@@ -1,34 +0,0 @@
----
-id: zoom
-title: Zoom
----
-
-## Documentation
-
-https://marketplace.zoom.us/docs/guides/auth/oauth
-
-## Configuration
-
-https://marketplace.zoom.us
-
-## Options
-
-The **Zoom Provider** comes with a set of default options:
-
-- [Zoom Provider options](https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/zoom.ts)
-
-You can override any of the options to suit your own use case.
-
-## Example
-
-```js
-import ZoomProvider from "next-auth/providers/zoom"
-...
-providers: [
-  ZoomProvider({
-    clientId: process.env.ZOOM_CLIENT_ID,
-    clientSecret: process.env.ZOOM_CLIENT_SECRET
-  })
-}
-...
-```

docs/docs/reference/06-adapters/00-overview.md

@@ -1,10 +0,0 @@
----
-title: Overview
----
-
-Auth.js / NextAuth.js database adapters.
-
-
-:::warning
-Auth.js (`@auth/*`) support is experimental.
-:::

docs/docs/reference/06-adapters/_category_.json

@@ -1,5 +0,0 @@
-{
-  "label": "Database adapters",
-  "collapsible": true,
-  "collapsed": true
-}

docs/docs/reference/09-warnings.md

@@ -1,15 +0,0 @@
----
-id: warnings
-title: Warnings
----
-
-A list of warnings from Auth.js that need your attention.
-
-
-## Debug enabled
-
-The `debug` option was evaluated to `true`. It adds extra logs in the terminal which is useful in development, but since it can print sensitive information about users, make sure to set this to `false` in production. In Node.js environments, you can for example set `debug: process.env.NODE_ENV !== "production"`. Consult with your runtime/framework on how to set this value correctly.
-
-## CSRF disabled
-
-You were trying to get a CSRF response from Auth.js (eg.: by calling a `/csrf` endpoint), but in this setup, CSRF protection via Auth.js was turned off. This is likely if you are not directly using `@auth/core` but a framework library (like `@auth/sveltekit`) that already has CSRF protection built-in. You likely won't need the CSRF response.

docs/docusaurus.config.js

@@ -1,391 +0,0 @@
-// @ts-check
-
-const fs = require("fs")
-const path = require("path")
-
-// list providers entries from @auth/core/providers/*.ts
-const coreSrc = "../packages/core/src"
-const providers = fs
-  .readdirSync(path.join(__dirname, coreSrc, "/providers"))
-  .filter((file) => file.endsWith(".ts") && !file.startsWith("oauth"))
-  .map((p) => `${coreSrc}/providers/${p}`)
-
-const typedocConfig = require("./typedoc.json")
-// @ts-expect-error
-delete typedocConfig.$schema
-
-/**
- * @param {string} name
- * @returns Record<string, any>
- */
-function createTypeDocAdapterConfig(name) {
-  const slug = name.toLowerCase().replace(" ", "-")
-
-  return {
-    id: slug,
-    plugin: [require.resolve("./typedoc-mdn-links")],
-    watch: process.env.TYPEDOC_WATCH,
-    entryPoints: [`../packages/adapter-${slug}/src/index.ts`],
-    tsconfig: `../packages/adapter-${slug}/tsconfig.json`,
-    out: `reference/adapter/${slug}`,
-    sidebar: {
-      indexLabel: name,
-    },
-  }
-}
-
-/** @type {import("@docusaurus/types").Config} */
-const docusaurusConfig = {
-  title: "Auth.js",
-  tagline: "Authentication for the Web.",
-  url: "https://authjs.dev",
-  baseUrl: "/",
-  favicon: "img/favicon.ico",
-  trailingSlash: false,
-  organizationName: "nextauthjs",
-  // TODO: remove this once ready
-  onBrokenLinks: "log",
-  projectName: "next-auth",
-  themeConfig: {
-    prism: {
-      theme: require("prism-react-renderer/themes/nightOwl"),
-      magicComments: [
-        {
-          className: "theme-code-block-highlighted-line",
-          line: "highlight-next-line",
-          block: { start: "highlight-start", end: "highlight-end" },
-        },
-      ],
-    },
-    algolia: {
-      appId: "OUEDA16KPG",
-      apiKey: "97c0894508f2d1d4a2fef4fe6db28448",
-      indexName: "next-auth",
-      searchParameters: {},
-      contextualSearch: false,
-      externalUrlRegex: "authjs\\.dev|next-auth\\.js\\.org",
-    },
-    navbar: {
-      title: "Auth.js",
-      logo: {
-        alt: "Auth.js Logo",
-        src: "img/logo/logo-xs.webp",
-      },
-      items: [
-        {
-          to: "/getting-started/introduction",
-          activeBasePath: "/getting-started/",
-          label: "Getting started",
-          position: "left",
-        },
-        {
-          to: "/guides",
-          activeBasePath: "/guides",
-          label: "Guides",
-          position: "left",
-        },
-        {
-          to: "/reference/core",
-          // TODO: change to this when the overview page looks better.
-          // to: "/reference",
-          activeBasePath: "/reference",
-          label: "Reference",
-          position: "left",
-        },
-        {
-          to: "/concepts/faq",
-          activeBasePath: "/concepts",
-          label: "Concepts",
-          position: "left",
-        },
-        {
-          type: "docsVersionDropdown",
-          position: "right",
-          dropdownActiveClassDisabled: true,
-          dropdownItemsAfter: [
-            {
-              to: "https://github.com/nextauthjs/next-auth/releases",
-              label: "All Releases",
-            },
-          ],
-        },
-        {
-          to: "https://www.npmjs.com/package/next-auth",
-          label: "npm",
-          position: "right",
-        },
-        {
-          to: "https://github.com/nextauthjs/next-auth",
-          label: "GitHub",
-          position: "right",
-        },
-      ],
-    },
-    announcementBar: {
-      id: "new-major-announcement",
-      content:
-        "<a target='_blank' rel='noopener noreferrer' href='https://next-auth.js.org'>NextAuth.js</a> is becoming Auth.js! 🎉 We're creating Authentication for the Web. Everyone included. Starting with SvelteKit, check out <a href='/reference/sveltekit'>the docs</a>. Note, this site is under active development.",
-      backgroundColor: "#000",
-      textColor: "#fff",
-    },
-    footer: {
-      links: [
-        {
-          title: "About Auth.js",
-          items: [
-            {
-              label: "Introduction",
-              to: "/getting-started/introduction",
-            },
-            {
-              html: `
-            <a target="_blank" rel="noopener noreferrer" href="https://vercel.com?utm_source=authjs&utm_campaign=oss">
-              <img
-                alt="Powered by Vercel"
-                style="margin-top: 8px"
-                height="32"
-                width="167"
-                src="https://raw.githubusercontent.com/nextauthjs/next-auth/main/docs/static/img/powered-by-vercel.svg"
-              />
-            </a>`,
-            },
-          ],
-        },
-        {
-          title: "Download",
-          items: [
-            {
-              label: "GitHub",
-              to: "https://github.com/nextauthjs/next-auth",
-            },
-            {
-              label: "NPM",
-              to: "https://www.npmjs.com/package/next-auth",
-            },
-          ],
-        },
-        {
-          title: "Acknowledgements",
-          items: [
-            {
-              label: "Contributors",
-              to: "/contributors",
-            },
-            {
-              label: "Sponsors",
-              to: "https://opencollective.com/nextauth",
-            },
-            {
-              label: "Images by unDraw",
-              to: "https://undraw.co/",
-            },
-          ],
-        },
-      ],
-      copyright: `Auth.js &copy; Balázs Orbán ${new Date().getFullYear()}`,
-    },
-    colorMode: {
-      respectPrefersColorScheme: true,
-    },
-    docs: {
-      sidebar: {
-        autoCollapseCategories: true,
-      },
-    },
-  },
-  presets: [
-    [
-      "@docusaurus/preset-classic",
-      {
-        docs: {
-          breadcrumbs: false,
-          routeBasePath: "/",
-          sidebarPath: require.resolve("./sidebars.js"),
-          editUrl: "https://github.com/nextauthjs/next-auth/edit/main/docs",
-          lastVersion: "current",
-          showLastUpdateAuthor: true,
-          showLastUpdateTime: true,
-          remarkPlugins: [require("@sapphire/docusaurus-plugin-npm2yarn2pnpm").npm2yarn2pnpm],
-          versions: {
-            current: {
-              label: "experimental",
-            },
-          },
-        },
-        theme: {
-          customCss: require.resolve("./src/css/index.css"),
-        },
-      },
-    ],
-  ],
-  plugins: [
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        id: "core",
-        plugin: [require.resolve("./typedoc-mdn-links")],
-        watch: process.env.TYPEDOC_WATCH,
-        entryPoints: ["index.ts", "adapters.ts", "errors.ts", "jwt.ts", "types.ts"].map((e) => `${coreSrc}/${e}`).concat(providers),
-        tsconfig: "../packages/core/tsconfig.json",
-        out: "reference/core",
-        sidebar: {
-          indexLabel: "index",
-        },
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        id: "sveltekit",
-        plugin: [require.resolve("./typedoc-mdn-links")],
-        watch: process.env.TYPEDOC_WATCH,
-        entryPoints: ["index.ts", "client.ts"].map((e) => `../packages/frameworks-sveltekit/src/lib/${e}`),
-        tsconfig: "../packages/frameworks-sveltekit/tsconfig.json",
-        out: "reference/sveltekit",
-        sidebar: {
-          indexLabel: "index",
-        },
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        ...createTypeDocAdapterConfig("Firebase"),
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        ...createTypeDocAdapterConfig("Dgraph"),
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        ...createTypeDocAdapterConfig("Prisma"),
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        ...createTypeDocAdapterConfig("Fauna"),
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        id: "typeorm",
-        plugin: [require.resolve("./typedoc-mdn-links")],
-        watch: process.env.TYPEDOC_WATCH,
-        entryPoints: [`../packages/adapter-typeorm-legacy/src/index.ts`],
-        tsconfig: `../packages/adapter-typeorm-legacy/tsconfig.json`,
-        out: `reference/adapter/typeorm`,
-        sidebar: {
-          indexLabel: "TypeORM",
-        },
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        ...createTypeDocAdapterConfig("DynamoDB"),
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        ...createTypeDocAdapterConfig("MongoDB"),
-      },
-    ],
-    [
-      "docusaurus-plugin-typedoc",
-      {
-        ...typedocConfig,
-        ...createTypeDocAdapterConfig("PouchDB"),
-      },
-    ],
-  ],
-}
-
-docusaurusConfig.headTags = [
-  {
-    tagName: "meta",
-    attributes: {
-      charSet: "utf-8",
-    },
-  },
-  {
-    tagName: "link",
-    attributes: {
-      rel: "canonical",
-      href: docusaurusConfig.url,
-    },
-  },
-  {
-    tagName: "meta",
-    attributes: {
-      property: "og:title",
-      content: docusaurusConfig.title,
-    },
-  },
-  {
-    tagName: "meta",
-    attributes: {
-      property: "og:description",
-      content: docusaurusConfig.tagline,
-    },
-  },
-  {
-    tagName: "meta",
-    attributes: {
-      property: "og:image",
-      content: `${docusaurusConfig.url}/img/og-image.png`,
-    },
-  },
-  {
-    tagName: "meta",
-    attributes: {
-      property: "og:url",
-      content: docusaurusConfig.url,
-    },
-  },
-  {
-    tagName: "meta",
-    attributes: {
-      name: "twitter:card",
-      content: "summary_large_image",
-    },
-  },
-  {
-    tagName: "meta",
-    attributes: {
-      name: "twitter:title",
-      content: docusaurusConfig.title,
-    },
-  },
-  {
-    tagName: "meta",
-    attributes: {
-      name: "twitter:description",
-      content: docusaurusConfig.tagline,
-    },
-  },
-  {
-    tagName: "meta",
-    attributes: {
-      name: "twitter:image",
-      content: `${docusaurusConfig.url}/img/og-image.png`,
-    },
-  },
-]
-
-module.exports = docusaurusConfig

docs/next-env.d.ts

@@ -0,0 +1,5 @@
+/// <reference types="next" />
+/// <reference types="next/image-types/global" />
+
+// NOTE: This file should not be edited
+// see https://nextjs.org/docs/basic-features/typescript for more information.

docs/next.config.mjs

@@ -0,0 +1,26 @@
+import withNextra from "nextra"
+import RemarkLinkRewrite from "remark-link-rewrite"
+
+export default withNextra({
+  theme: "nextra-theme-docs",
+  themeConfig: "./theme.config.jsx",
+  mdxOptions: {
+    format: "detect",
+    remarkPlugins: [
+      [
+        RemarkLinkRewrite,
+        {
+          replacer(url) {
+            if (url.includes(".md")) {
+              url = url.replace(/\.md$/, "").replace(".md#", "#")
+            }
+            if (url.startsWith("https://authjs.dev")) {
+              url = url.replace("https://authjs.dev", "")
+            }
+            return url
+          },
+        },
+      ],
+    ],
+  },
+})()

docs/package.json

@@ -1,52 +1,33 @@
 {
-  "private": true,
-  "repository": "https://github.com/nextauthjs/next-auth",
   "name": "docs",
+  "version": "0.0.1",
+  "description": "",
+  "main": "index.js",
   "scripts": {
-    "start": "TYPEDOC_WATCH=true docusaurus start --no-open",
-    "dev": "pnpm providers && pnpm snippets && pnpm start",
-    "build": "pnpm providers && docusaurus build",
-    "docusaurus": "docusaurus",
-    "swizzle": "docusaurus swizzle",
-    "deploy": "docusaurus deploy",
-    "serve": "docusaurus serve",
-    "clear": "docusaurus clear",
-    "providers": "node scripts/generate-providers.mjs",
-    "snippets": "node scripts/generate-snippets.mjs"
+    "typedoc": "typedoc",
+    "dev": "TYPEDOC_WATCH=1 pnpm typedoc & next dev",
+    "start": "next start",
+    "build": "next build"
   },
+  "keywords": [],
+  "author": "ndom91 <yo@ndo.dev> (https://ndo.dev/)",
+  "license": "MIT",
   "dependencies": {
-    "@mdx-js/react": "1.6.22",
-    "@sapphire/docusaurus-plugin-npm2yarn2pnpm": "1.1.4",
-    "classnames": "^2.3.2",
-    "mdx-mermaid": "1.2.2",
-    "mermaid": "9.0.1",
-    "prism-react-renderer": "1.3.5",
+    "@codesandbox/sandpack-react": "^2.0.6",
+    "framer-motion": "^8.4.3",
+    "next": "13.2.4",
+    "nextra": "^2.2.19",
+    "nextra-theme-docs": "^2.2.19",
     "react": "^18.2.0",
     "react-dom": "^18.2.0",
-    "react-marquee-slider": "^1.1.5",
-    "styled-components": "5.3.6"
+    "remark-link-rewrite": "^1.0.6",
+    "typedoc": "^0.23.24",
+    "typedoc-plugin-markdown": "next"
   },
   "devDependencies": {
-    "@docusaurus/core": "2.2.0",
-    "@docusaurus/eslint-plugin": "2.2.0",
-    "@docusaurus/module-type-aliases": "2.2.0",
-    "@docusaurus/preset-classic": "2.2.0",
-    "@docusaurus/theme-common": "2.2.0",
-    "@docusaurus/types": "2.2.0",
-    "docusaurus-plugin-typedoc": "1.0.0-next.2",
-    "typedoc": "^0.23.24",
-    "typedoc-plugin-markdown": "4.0.0-next.2"
-  },
-  "browserslist": {
-    "production": [
-      ">0.2%",
-      "not dead",
-      "not op_mini all"
-    ],
-    "development": [
-      "last 1 chrome version",
-      "last 1 firefox version",
-      "last 1 safari version"
-    ]
+    "autoprefixer": "^10.4.13",
+    "eslint-config-next": "^13.2.4",
+    "postcss": "^8.4.21",
+    "tailwindcss": "^3.2.4"
   }
 }

docs/pages/404.mdx

@@ -0,0 +1,5 @@
+import { NotFoundPage } from 'nextra-theme-docs'
+
+# 404 - This page could not be found
+
+<NotFoundPage />

docs/pages/500.mdx

@@ -0,0 +1,5 @@
+import { ServerSideErrorPage } from 'nextra-theme-docs'
+
+# 500 - Internal Server Error
+
+<ServerSideErrorPage />

docs/pages/_app.mdx

@@ -0,0 +1,5 @@
+import "../styles/index.css"
+
+export default function NextraApp({ Component, pageProps }) {
+  return <Component {...pageProps} />
+}