next-auth

thanks for the link! i hear you on not having to build for everyone and it's good to take a stance and not be for everyone / every use case. dhh talked about this at railsworld recently [0]. i think i've got it working ok with the second request to update the session (as suggested here [1]). [0]: https://www.youtube.com/watch?v=zPBbHu-BKpQ [1]: https://github.com/nextauthjs/next-auth/discussions/9715

I use authjs (aka next-auth) and recently documented that Google login requests additional access every time the user logs in[1]. I created an issue with a repro, although the maintainers moved it to discussions. It seems that the problem is with Google, but in that case I don't understand why the next-auth example works fine[2]. There are other users affected. If anyone knows how to solve this problem, I would appreciate it if you could say so. https://github.com/nextauthjs/next-auth/discussions/11160 https://next-auth-example.vercel.app/

from time to time config is just not willing to sit there in a list. it needs to be computed. just an example from a few days ago. someone needs to pull data from some remote service (maybe Vault), or generation of keys/entropy/etc. [0][1] of course this just means folks should wrap the whole thing in a program. but that's getting inefficient fast if every layer only accepts "env vars" or a plain JSON file. [0] https://github.com/nextauthjs/next-auth/pull/9638#issuecomme... [1] https://github.com/nextauthjs/next-auth/pull/9638#issuecomme...