Files
cozsweet-frontend-nextjs/docs/nextauth/docs/providers/atlassian.md
T
admin d70e61f92e refactor(auth): switch to class-based social login and v4 route handler
Migrate from function-based social login helpers (`facebookLogin`, `googleLogin`)
to class-based services (`new FacebookLogin().signIn()`, `new GoogleLogin().signIn()`),
updating call sites in `AuthFacebookPanel` and `SplashButton` with try/catch error
handling. The NextAuth route handler is also refactored to the v4 pattern, importing
pre-built `GET` / `POST` exports from `@/lib/auth/nextauth` instead of constructing
the handler inline with `NextAuth(authOptions)`.
2026-06-10 15:34:52 +08:00

1.2 KiB

id, title
id title
atlassian 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:

You can override any of the options to suit your own use case.

Example

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)":

:::warning To enable access to Jira Platform REST API you must enable User Identity API and add read:me to your provider scope option. :::