Custom fields for Credentials Provider

Describe the feature

I would like to suggest a custom/optional field in the user interface object to store additional data. F.e when logging in with Strapi using Credential flow, the server will return a JWT. This token needs to stay unaltered otherwise the secret is no longer valid. I would like to propose a extra optional field for users, so that they can add in content that can be then safely stored within the encoded session jwt. By using getToken in Nitro we could then reacquire the original raw JWT token from Strapi.

Additional information

Within the […].ts auth catch all endpoint:

`if (user) {

      const u = {
        id: user.id,
        name: user.user.username,
        // Passing the OG JWT through the email field.
        email: user.jwt
      };

      return u;
    } else {
      // If you return null then an error will be displayed advising the user to check their details.
      return null;

      // You can also Reject this callback with an Error thus the user will be sent to the error page with the error message as a query parameter
    }`

And then in Nitro Api I hack it out the email field currently with getToken: `const token = await getToken({ event });

const settings = {
  method: "GET",
  headers: {
    "Content-Type": "application/json",
    Authorization: "Bearer " + token.email,
  },
};`

No response

[BracketJohn]

Hey @jorgv, Hey @darwebdb,

this is a question that has been answered by @JoaoPedroAS51 here: https://github.com/sidebase/nuxt-auth/issues/61#issuecomment-1330946022

It will also be part of our documentation once #90 is merged: https://sidebase.io/nuxt-auth/recipes/custom-session-data

I’m closing this issue for now, please open a new one if there’s any further need for clarification (:

Thanks to both of you (:

[jorgv]

Thanks for your reply @BracketJohn

I am using a similar situation like @darwebdb. We have a remote backend, so we use the credentials provider. We authenticate the user and we get a token and the user information as response:

  data: {
    token: 'eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYX',
    user: {
      id: '2',
      username: 'myuser',
      firstName: 'John',
      lastName: 'Doe',
      email: '[e-mail]'
     otherThings: {...}
      }
  }      

In the authorize function from the credentials provider, I can pass only name, email and image. So like @darwebdb I am passing the backend token to the image field in order to access it after with the useSession and getSession

Data: {
  "user": {
    "name": "John",
    "email": "[e-mail]",
    "image": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYX"
  },
  "expires": "2022-12-18T08:34:11.586Z"
}

So, my question is how can I store the rest of the response fields in the session, can I do it during the authorize function? or how can I pass it to a callback so I can store it.

Or is it better to extend the user interface with the fields that I need, if this is the best way how do I replace the typeinterface for the custom one, as the link you provided from AuthNext I already have the custom type/next-auth.ts file but I am not sure how to replace it in the module.

thanks