Nico Domino

@ppulwey no updates that I'm aware of. @akoskm do you still plan on working on this? :pray:

Yeah so the issue is that many of the adapter's don't work in middleware (edge runtimes), as they rely on Node.js APIs that aren't available in the JS runtimes hosting...

Hey thanks for your interest! However, we'd like to avoid making changes like this to v4 atm. Does setting `NEXTAUTH_URL` to include only the basePath (i.e. `http://localhost:3000/sso`) work for yuo?

@ammmze okay gotcha, yeah we changed the default behaviour of that in v5 but I couldn't remember how v4 behaved in detail. Okay let me have a think abuot this,...

@JipSterk thanks for reopening this! Could you also add some tests for this new model?? See the `adapter-prisma` `Authenticator` tests for an example :pray:

@JipSterk sorry for the delay, webauthn hasn't been our number 1 priority as we'd like to get the core functionality ironed out and v5 + new docs out before we...

@JipSterk we successfully shipped the new docs the other day! :partying_face: But we also merged the [rewritten Drizzle adapter](https://github.com/nextauthjs/next-auth/pull/10479), so you'll probably have to modify a decent amt of things...

@JipSterk awesome thanks for the quick turnaround! So I ran the tests locally as well and ran into the following issues: 1. In both the `pg` and `mysql` suites the...

Hope you don't mind, I pushed a little PR updating the `getAuthenticator` method in `pg`,`mysql` and `sqlite` files. ```diff async getAuthenticator(credentialID) { const authenticator = await client .select() .from(authenticatorsTable) .where(eq(authenticatorsTable.credentialID,...

> Thanks for updating the pr! > I just tested again and both `pg` as `sqlite` run their tests & succeed. mysql however does not. > instead it throws the...