Skip to content

Bungie Provider does not work #12978

@yashranjan1

Description

@yashranjan1

Provider type

Bungie

Environment

OS: NixOS 24.11
Node Version: v23.10.0

package.json version info:
"next": "^15.2.3",
"next-auth": "5.0.0-beta.25",
"react": "^19.0.0",

Reproduction URL

failed-next-auth-prov

Describe the issue

Theres two problems here.

  1. LSP Issue:
    The LSP throws a type error when I define the provider options as shown in the docs. The error states that 'headers' does not exist in the type 'OAuthUserConfig'

Here is how I have defined them

    Bungie({
      clientId: env.AUTH_BUNGIE_ID,
      clientSecret: env.AUTH_BUNGIE_SECRET,
      headers: { "X-API-Key": env.AUTH_BUNGIE_API_KEY },
    }),

Link to the definition given in the docs

  1. Auth Callback error
    I get an auth callback error when i try to sign in using a bungie account, this is what the error looks like
[auth][error] OAuthCallbackError: OAuth Provider returned an error. Read more at https://errors.authjs.dev#oauthcallbackerror
    at handleOAuth (/home/yash/Documents/black-armory/.next/server/chunks/e044d_@auth_core_4bd949b2._.js:3284:19)
    at async callback (/home/yash/Documents/black-armory/.next/server/chunks/e044d_@auth_core_4bd949b2._.js:3782:41)
    at async AuthInternal (/home/yash/Documents/black-armory/.next/server/chunks/e044d_@auth_core_4bd949b2._.js:4835:24)
    at async Auth (/home/yash/Documents/black-armory/.next/server/chunks/e044d_@auth_core_4bd949b2._.js:5099:34)
    at async AppRouteRouteModule.do (/home/yash/Documents/black-armory/node_modules/next/dist/compiled/next-server/app-route-turbo.runtime.dev.js:26:34112)
    at async AppRouteRouteModule.handle (/home/yash/Documents/black-armory/node_modules/next/dist/compiled/next-server/app-route-turbo.runtime.dev.js:26:41338)
    at async doRender (/home/yash/Documents/black-armory/node_modules/next/dist/server/base-server.js:1513:42)
    at async DevServer.renderToResponseWithComponentsImpl (/home/yash/Documents/black-armory/node_modules/next/dist/server/base-server.js:1915:28)
    at async DevServer.renderPageComponent (/home/yash/Documents/black-armory/node_modules/next/dist/server/base-server.js:2403:24)
    at async DevServer.renderToResponseImpl (/home/yash/Documents/black-armory/node_modules/next/dist/server/base-server.js:2440:32)
    at async DevServer.pipeImpl (/home/yash/Documents/black-armory/node_modules/next/dist/server/base-server.js:1007:25)
    at async NextNodeServer.handleCatchallRenderRequest (/home/yash/Documents/black-armory/node_modules/next/dist/server/next-server.js:305:17)
    at async DevServer.handleRequestImpl (/home/yash/Documents/black-armory/node_modules/next/dist/server/base-server.js:899:17)
    at async /home/yash/Documents/black-armory/node_modules/next/dist/server/dev/next-dev-server.js:371:20
    at async Span.traceAsyncFn (/home/yash/Documents/black-armory/node_modules/next/dist/trace/trace.js:157:20)
    at async DevServer.handleRequest (/home/yash/Documents/black-armory/node_modules/next/dist/server/dev/next-dev-server.js:368:24)
    at async invokeRender (/home/yash/Documents/black-armory/node_modules/next/dist/server/lib/router-server.js:237:21)
    at async handleRequest (/home/yash/Documents/black-armory/node_modules/next/dist/server/lib/router-server.js:428:24)
    at async requestHandlerImpl (/home/yash/Documents/black-armory/node_modules/next/dist/server/lib/router-server.js:452:13)
    at async Server.requestListener (/home/yash/Documents/black-armory/node_modules/next/dist/server/lib/start-server.js:158:13)
 GET /api/auth/callback/bungie?error=invalid_scope&error_description=Scope%20is%20always%20configured%20value.%20Do%20not%20specify%20scope%20parameter. 302 in 23ms

I'm fairly certain I have followed the instructions on the doc page well and setup the Application on bungies website the way the Auth.js docs describe. If this is something stupid I have done I am so sorry for wasting your time!

Thanks so much for all the help

How to reproduce

Try running the app and logging in.

Expected behavior

It should successfully log in

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingproviderstriageUnseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions