Enhance Spotify provider to support custom scopes via authorization params

[sshuvoo]

Provider type

Spotify

Environment

## System:
    - OS: Windows 11 10.0.22631
    - CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz
    - Memory: 1.19 GB / 7.88 GB
## Binaries:
    - Node: 20.12.0 - C:\Program Files\nodejs\node.EXE
    - npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
## Browsers:
    - Edge: Chromium (127.0.2651.74)
    - Internet Explorer: 11.0.22621.3527
## npmPackages:
    - next: 14.2.5 => 14.2.5
    - next-auth: ^5.0.0-beta.20 => 5.0.0-beta.20
    - react: ^18 => 18.3.1

Reproduction URL

https://github.com/sshuvoo/next-auth-example

Describe the issue

The Spotify provider in Auth.js doesn't support setting custom scopes through the authorization.params.scope option, unlike other providers. This inconsistency makes it difficult to configure custom scopes for Spotify in the same way as other OAuth providers.

Currently, the Spotify provider has a hardcoded scope in its authorization URL:

{authorization:
  "https://accounts.spotify.com/authorize?scope=user-read-email",}

This means that users can't easily customize the scopes without overriding the entire authorization URL. I've tried to use the standard configuration method used for other providers:

providers: [
   Spotify({
      authorization: {
         params: {
            scope: 'user-top-read user-read-email',
         },
      },
   }),
]

However, this doesn't work as expected, and the default "user-read-email" scope is still used.

Current workaround (After analyzing source code (Spotify.ts)):

Spotify({
   authorization: `https://accounts.spotify.com/authorize?scope=${encodeURIComponent('custom scopes here')}`,
})

How to reproduce

Set up a new Auth.js project with the Spotify provider.
Try to configure custom scopes using the standard method:

export const { handlers, auth } = NextAuth({
   providers: [
      Spotify({
         authorization: {
            params: {
               scope: 'user-top-read user-read-email',
            },
         },
      }),
   ],
})

Initiate the Spotify authentication flow.
Observe that the authorization URL still only includes the default "user-read-email" scope.

Expected behavior

The Spotify provider should respect the authorization.params.scope option, similar to other OAuth providers in Auth.js. When custom scopes are specified, they should be included in the authorization URL sent to Spotify.

The expected behavior would allow users to configure Spotify scopes like this:

Spotify({
   authorization: {
      params: {
         scope: 'user-top-read user-read-email',
      },
   },
})

This configuration should result in an authorization URL that includes all the specified scopes, allowing users to request the necessary permissions from Spotify without having to override the entire authorization URL.

[balazsorban44]

Should be fixed holistically, not just for Spotify. PRs welcome!

[github-actions]

This issue was marked with the good first issue label by a maintainer.

This means that it is a good candidate for someone interested in contributing to the project, but does not know where to start.

Have a look at the Contributing Guide first.

This will help you set up your development environment to get started. When you are ready, open a PR, and link back to this issue in the form of adding Fixes #1234 to the PR description, where 1234 is the issue number. This will auto-close the issue when the PR gets merged, making it easier for us to keep track of what has been fixed.

Please make sure that - if applicable - you add tests for the changes you make.

If you have any questions, feel free to ask in the comments below or the PR. Generally, you don't need to @mention anyone directly, as we will get notified anyway and will respond as soon as we can)

Note

There is no need to ask for permission "can I work on this?" Please, go ahead if there is no linked PR 🙂

[balazsorban44]

possibly need a fix here:

https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/lib/utils/merge.ts

and/or

next-auth/packages/core/src/lib/utils/providers.ts

Line 132 in 6377582

function normalizeEndpoint(

[Zamoca42]

possibly need a fix here:

https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/lib/utils/merge.ts

I believe the code is related to the PR I submitted (#11685) and the issue discussed #9448 (comment).

[Withervoid77]

Same issue here but with the Discord provider. From what I see, you’re right—the only viable solution is to override the default authorization URL. Hopefully, this gets fixed in the future so we can add scopes much more easily.

[balazsorban44]

#11685 is merged, will be out in the next release! Thank you @Zamoca42!

[nic-vo]

Oh hey, glad this was fixed!

When I wrote that comment, I noticed that there were a few other issues related to custom authorization configs for other providers. The adapters were being patched with the new authorization object shape; moving forward, providers that still have their original string primitive authorization URLs should allow configuration as per the docs

Thanks @Zamoca42