Using JWS in v4 getToken not working.

[transformmindgarden]

I believe there may be a bug with the overriding of the decode functionality. When you override the encode and decode, the login works properly and your session gets stored properly. However, if you attempt to get the token using getToken() (import { getToken } from "next-auth/jwt") it will call the default decoder in index.js of the next-auth/jwt module not the decode method used to override.

Overwriting the decode in the index.js of next-auth/jwt resolves the issue of getToken() not working, but is undesirable.

Am I missing something? or is this a bug with overriding encode and decode? using version 4.3.1

Here is an example of JWS encode/decode functions in [..nextauth].js:

jwt:{
	maxAge: 15000,
	async encode(params: {
		token: JWT
		secret: string
		maxAge: number
	  }): Promise<string> {
		  var _jose = require("jose");
		  var _uuid = require("uuid");
		  const now = () => Date.now() / 1000 | 0;
		  const jwt = await new _jose.SignJWT(params.token)
		    .setProtectedHeader({ alg: 'HS256' })
		    .setIssuedAt().setExpirationTime(now() + params.maxAge).setJti((0, _uuid.v4)())
		    .sign(Buffer.from(params.secret));
		  return jwt;
	  },

	async decode(params: {
		token: string
		secret: string
	  }): Promise<JWT | null> {
		var _jose = require("jose");
		if (!params.token) return null;
 		const { payload, protectedHeader } = await _jose.jwtVerify(params.token, Buffer.from(params.secret), {});
		return payload;
	  },
  },