Handle current session when auth via new provider

[lavcraft]

Hello, i can't find how to handle my case in documentation.
My case:

1. SignIn via Custom OAuth 2 Provider
2. SignIn via Google account after
   I need to save access_token`s to current session, but after second signIn, new session is completely replace old.

How to access to current authentication data before create new session in callbacks?

[balazsorban44]

if you are using a stateless cookie persisted JWT session (which is the default), you don't have that option. you will need a database/adapter to persist the user data between sessions https://next-auth.js.org/adapters/overview

[lavcraft]

May be. But more flexible way - get ability to decide, which token/session is appropriate, to user. Because in some cases user want replace session, but in other cases want to merge or extend with previous. Also, this approach provide more safely backward compatibility

[balazsorban44]

Want to write up a feature request/RFC? We could ask the people what they think.

[lavcraft]

Sure, where is guide for feature request?

[balazsorban44]

https://github.com/nextauthjs/next-auth/issues/new?assignees=&labels=enhancement&template=feature_request.yaml

[lavcraft]

Done: #2988