feat: rename session strategy

[balazsorban44]

This PR makes it hopefully more clear how the user can use the different session strategies.

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://next-auth.js.org/faq#json-web-tokens

Docs: nextauthjs/docs#105

[ubbe-xyz]

💯

[zigang93]

still get CALLBACK_CREDENTIALS_JWT_ERROR ,
even I already set the strategy to jwt

session: {
    strategy: 'jwt',
  },

[davecarlson]

Same as above, unable to get a csrf token:

[next-auth][error][CALLBACK_CREDENTIALS_JWT_ERROR]
https://next-auth.js.org/errors#callback_credentials_jwt_error Signin in with credentials only supported if JWT strategy is enabled UnsupportedStrategy [UnsupportedStrategyError]: Signin in with credentials only supported if JWT strategy is enabled

[aokigit]

Having the exact same problem as the two people above me. Tried both the old and new strategy way and always receiving the CALLBACK_CREDENTIALS_JWT_ERROR error.

[balazsorban44]

Addressed already.

#3216 reported this, the fix has landed, release coming 🔜. Use the version here ttps://github.com//pull/3217#issuecomment-970646869 or patch-package if you cannot wait.

[rabin-nyaundi]

I'm having the same issue with next-auth v4.

[next-auth][error][CALLBACK_CREDENTIALS_JWT_ERROR] 
https://next-auth.js.org/errors#callback_credentials_jwt_error Signin in with credentials only supported if JWT strategy is enabled UnsupportedStrategy [UnsupportedStrategyError]: Signin in with credentials only supported if JWT strategy is enabled

even after setting

session:{
      strategy: 'jwt'
}

[renchris]

Is there a way to use next-auth for using jwt tokens in session storage but not using it nor including a provider for user login authentication?