Session Cookie with knex.js

[codelover2k]

I am trying to switch to Next.js and before that I used Express.

For authentication I used express-session and connect-session-knex.
The great thing about connect-session-knex is that it creates the data table for you and if something changes or if you delete that table, it just creates a fresh one for you.

Furthermore it automatically deletes sessions from the database if they are not valid anymore, so you can set the time how many times the database should be checked for dead sessions.
In my case these modules check the database every 60 minutes and deletes sessions to keep the table small and fast as possible.

I would like to know if you have these features also in next-auth?

• Will the required data table be created automatically and also updated if needed? (for example if a new version is there)

• can you also use knex.js? (if yes an example would be nice)

• does it also check the database and clean dead sessions if it find any?

Would be great if someone could help me with that :)

[iaincollins]

• Will the required data table be created automatically and also updated if needed? (for example if a new version is there)

If the synchronize option is set to true in the database options NextAuth.js will automatically create or update any tables needed (this is handled by TypeORM), however enabling this option is not currently recommended in production as it does not actually perform a migration and could lead to data loss between releases.

The synchronize option is intended to make it easier to get started, but SQL schema changes need to be handled manually currently - with this in mind, we generally avoid making changes to the schema (until we have improved support for handling migrations). There are some changes I would like to make that require an SQL schema change, but I'm currently not focusing on them for that reason. I anticipate we will have migration support at some point, for either TypeORM, Prisma or both.

Note: We also maintain SQL schemas (e.g. MySQL schema, Postgres schema) for the current version.

• can you also use knex.js? (if yes an example would be nice)

NextAuth.js ships with adapters that use TypeORM and Prisma and supports MySQL, Postgres, Microsoft SQL Server, MongoDB (and other databases compatible with them). To use another database or ORM you can create a custom adapter.

You can also pass a database connection string to NextAuth.js and let it handle it's own connection without worrying about it, and connect to the database from your own application using whatever method you want.

• does it also check the database and clean dead sessions if it find any?

Not currently. I expect this will be something we will add to the default database adapter fairly soon.

[codelover2k]

thanks for response Iain, I will try it out!
it would be great to have an example of the session cookie based strategy, because in many cases where you need authentication, a session based cookie is recommended and better than JWTs.

[stale]

Hi there! It looks like this issue hasn't had any activity for a while. It will be closed if no further activity occurs. If you think your issue is still relevant, feel free to comment on it to keep ot open. Thanks!

[stale]

Hi there! It looks like this issue hasn't had any activity for a while. To keep things tidy, I am going to close this issue for now. If you think your issue is still relevant, just leave a comment and I will reopen it. (Read more at #912) Thanks!