Is it possible to have a database model that associates Accounts with Sessions instead of Users?

[william-will-angi]

I am trying to determine whether next-auth is appropriate for our use case. It seems like it is not based on the database schema described here: https://authjs.dev/concepts/database-models.

For some context, I am using next-auth for a single provider (Keycloak) and I never plan to add any additional providers.

I got one of the database adapters "working", however with some experimenting it seems that this has a massive downside:

• Each account is associated with the User table, and NOT the Session table. Each time a user signs in, a new access/refresh token is given by Keycloak. But the Account table will only ever contain one set of these. For apps that use access/refresh tokens, this seems to have some implications for users signing in with multiple devices.
  • From the admin side, if we want to invalidate a session, it becomes difficult because we don't know which of the keycloak sessions is being stored in next-auth without doing some introspection
  • If a user executes a backchannel logout for keycloak (invalidating the keycloak session) on any device, that will automatically invalidate the access/refresh token being used on all other devices that user has up.

Is there an easy way to have the Account table associated with sessions instead of users? Looking at the adapter pattern, it doesn't seem possible without abusing the existing models. If not, I am starting to think next-auth is the wrong solution for our use case (which is fine, but I would like to verify this isn't possible before trying to roll my own auth implementation).