Great tutorial! Just finished this tutorial and link form which you fetch user data from Google provider is no longer valid. In Google documentation I found a new one, which works. My question is: how often does Google change this link ? In our code all google auth functionality depends on it, if it changed - nothing works 🤨 and we need to manually go into code and change it every time google changes it, or what ? Am I only one who founds this element of Lucia auth a weak spot ?
@@ugurcodes It would be amazing if you could go into more depth with refreshing the token in the background, if user was signed in with google or credentials.
I may have missed something, but at what stage do we check and delete session data in cookies? I don't mean when you log out of your account, but if the session has expired
does Lucia supports react native app with next.js fullstack? i am looking for common auth system for my fullstack app written in next.js and want to authenticate mobile app on it. nextAuth cant do that .. does lucia support?
i am now using neon serverless as my pg in the cloud but i realized that it does not support transactions with https and i have to modify it to the weebsocket that neon offers, did you have to connect lucia with neon serverless?
@@fabienpineau1580 yes i read the documentacion for transactions in neon serverless, do you need to create anew instance Pool conection from @neondatabase/serverless and to conect with drizzle used import drizzle-orm/neon-serverless example: const client = new Pool({ connectionString: env.DATABASE_URL}); const db = drizzle(client, { schema }); now you can use db.transaction
hmm, it's not exactly related to auth topic but drizzle query would be: import { count } from 'drizzle-orm' await db.select({ value: count(userTable.id) }).from(userTable); and you can create a new server action that returns the result. Let me know if you need further help :)
I got it working, thank you! One thing I would suggest is not setting the id of user to be the id of the google account it might be confusing to have two records in different tables with the same id. I used generateId(15) and changed the where clauses so that the id strategy of user is always the same whetether it's from oauth or email/pwd
You said that you can reuse regular account (mail and password) when you have a google account with the same email. I didnt see you trying to login with email and password with the same email. Please explain how you can reuse accounts, because when you sign up with google the password should be null. Then after you logout , how you login with mail and password ? The obvious answer is that you need to make a regular account before sign up with google. But let;s say you sign first with google, then trying to make a regular account with the same mail. It wont work because email already exists, and also you cant login beause password is null, and that results in a error if not treated. [But anyways, your fetching the existing user from db was based on id, not email (user.Id === google.Id). The id was google id, as if you never thought about facebook or regular accounts. From the beginning you were against reusing accounts in code] Also , if you have a facebook account beside google (same mail) what would be the name saved in user table ? So, I think that this is the reason that 'some applications' (18:45) dont allow reusing the email. Because it is not possible if you dont strictly create an account before any ouath signup. And that's exactly the point of oauth: to avoid creating a password based account.
Great tutorials on Lucia Ugur, thank you! You explain things very clearly, well done.
Amazing, I'm tired reading more than 3 docs and Comment back and forth, Just to finish the google oauth with lucia.
Damn! I'm glad it helped you :)
Great tutorial! Just finished this tutorial and link form which you fetch user data from Google provider is no longer valid. In Google documentation I found a new one, which works. My question is: how often does Google change this link ? In our code all google auth functionality depends on it, if it changed - nothing works 🤨 and we need to manually go into code and change it every time google changes it, or what ? Am I only one who founds this element of Lucia auth a weak spot ?
Amazing keep the lucia tutorials going!
Thank you and will do! Let me know if you have a topic that you'd like to see
@@ugurcodes It would be amazing if you could go into more depth with refreshing the token in the background, if user was signed in with google or credentials.
@@ugurcodes Also where can I findyour code, I can't find your github?
This is awesome authentication lucia, Love your vedios can we get the microsoft provider as well for it?.
I may have missed something, but at what stage do we check and delete session data in cookies? I don't mean when you log out of your account, but if the session has expired
does Lucia supports react native app with next.js fullstack? i am looking for common auth system for my fullstack app written in next.js and want to authenticate mobile app on it. nextAuth cant do that .. does lucia support?
Great video, but how can we get user data on client side, does Lucia provide any function for that
Hi! I've just recorded a video about it! Sorry for the late reply.
You can checkout the last video I published
Take care,
Ugur
i am now using neon serverless as my pg in the cloud but i realized that it does not support transactions with https and i have to modify it to the weebsocket that neon offers, did you have to connect lucia with neon serverless?
did you find a solution?
@@fabienpineau1580 yes i read the documentacion for transactions in neon serverless, do you need to create anew instance Pool conection from @neondatabase/serverless and to conect with drizzle used import drizzle-orm/neon-serverless
example:
const client = new Pool({ connectionString: env.DATABASE_URL});
const db = drizzle(client, { schema });
now you can use db.transaction
Can you help writing a code to display the user count from the db for this project?
hmm,
it's not exactly related to auth topic but drizzle query would be:
import { count } from 'drizzle-orm'
await db.select({ value: count(userTable.id) }).from(userTable);
and you can create a new server action that returns the result. Let me know if you need further help :)
Would love to see you implement it in the next video ^^@@ugurcodes
sooo cool bro! can we have the github repo?
Hey! thanks:)
Checkout oauth branch
github.com/ugurkellecioglu/next-14-lucia-auth-postgresql-drizzle-typescript-example
Cool video, can u update the repo so that it's easier to copy code instead of retyping from video pls?
Code is available, please check oauth branch
amazing! tysm@@ugurcodes
I got it working, thank you! One thing I would suggest is not setting the id of user to be the id of the google account it might be confusing to have two records in different tables with the same id. I used generateId(15) and changed the where clauses so that the id strategy of user is always the same whetether it's from oauth or email/pwd
@@baptiste6436 yes! I realized that after recording video. Thanks for the suggestion 🙏
You said that you can reuse regular account (mail and password) when you have a google account with the same email.
I didnt see you trying to login with email and password with the same email.
Please explain how you can reuse accounts, because when you sign up with google the password should be null. Then after you logout , how you login with mail and password ? The obvious answer is that you need to make a regular account before sign up with google. But let;s say you sign first with google, then trying to make a regular account with the same mail. It wont work because email already exists, and also you cant login beause password is null, and that results in a error if not treated.
[But anyways, your fetching the existing user from db was based on id, not email (user.Id === google.Id). The id was google id, as if you never thought about facebook or regular accounts. From the beginning you were against reusing accounts in code]
Also , if you have a facebook account beside google (same mail) what would be the name saved in user table ?
So, I think that this is the reason that 'some applications' (18:45) dont allow reusing the email. Because it is not possible if you dont strictly create an account before any ouath signup. And that's exactly the point of oauth: to avoid creating a password based account.
Where is the repo?
Hey!
github.com/ugurkellecioglu/next-14-lucia-auth-postgresql-drizzle-typescript-example
can you please edit your videos before uploading, it's hard to learn when it breaks here and there and we go in to a rabbit hole to fix it