Unnecessary requirement for secret and salt in getToken when raw is set to true

[alimorgaan]

Environment

 System:
    OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (8) x64 Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz
    Memory: 16.27 GB / 19.20 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 20.11.0 - /usr/bin/node
    Yarn: 1.22.21 - /usr/bin/yarn
    npm: 10.8.2 -
    pnpm: 9.6.0 - ~/.local/share/pnpm/pnpm
  Browsers:
    Brave Browser: 129.1.70.117
    Chrome: 129.0.6668.58
  npmPackages:
    next: ^14.0.3 => 14.2.5 
    next-auth: ^5.0.0-beta.20 => 5.0.0-beta.20 
    react: ^18.3.1 => 18.3.1 

Reproduction URL

https://github.com/alimorgaan/next-auth-getToken-raw-issue/

Describe the issue

In the getToken helper function from next-auth/jwt, setting raw: true should return the token without requiring the secret or salt. However, currently, the function throws an error asking for both secret and salt even when raw is set to true.

This seems unnecessary because when raw: true is used, the function should return the raw token directly without needing any decoding or verification, which usually requires the secret and salt.

What I’ve tried so far:

• i attempted passing any dummy string to avoid throwing error it worked fine

How to reproduce

1. Import the getToken function from next-auth/jwt.
2. Use the following code to call getToken with raw: true:

import { getToken } from "next-auth/jwt";

const token = await getToken({
    req: request,
    raw: true,
});

3. Do not provide secret or salt in the configuration.
4. Observe the error requesting the secret and salt.

Expected behavior

When using raw: true, the getToken function should return the token as-is without requiring the secret or salt, since no verification or decoding should occur in this case. The current behavior of throwing an error requesting these fields is unexpected.