Add ability to update the session/jwt from the server

[camsloanftc]

Description 📓

The new update function from useSession is good, but it has to be triggered from the client.

It would be great if we could trigger the updates from the server.

I like how blitzjs handles this with a $setPublicData function. (It's also nice to have the $setPrivateData function as well, but I can live without that).

I think in most cases this would be a more elegant way to update the session, rather than having to authorize and validate the client sessions from the current update implementation.

How to reproduce ☕️

N/a

Contributing 🙌🏽

Yes, I am willing to help implement this feature in a PR

[DiegoGonzalezCruz]

Hi! Do you think that would be useful to update other users jwt?

[camsloanftc]

I don’t think you could set another users JWT like this since JWT is stateless, and no info is retained on the server.

If you used database sessions then you could update sessions for other users by a similar technique.

[khuezy]

I think this would be useful. I currently hack around this by manually encoding/decoding the next-auth.session-token to update it.

[maccman]

I definitely think this makes sense. I want to store some redirect params in there.

[itsbetma]

I think it can be a great feature, currently, I am implementing a feature that would take advantage of this.

[knightrun]

I need a feature to update sessions on the server in my project. Is this feature under development? If so, when do you expect it to be completed?