I recently came across with your videos. I found these videos extremely easy to understand and helpful. Thank you so much for your time and efforts for making such content.

@Computerix

2 ай бұрын

Thank you so much for your comment Jay! More videos coming soon !

Please make full stack apps with nestjs , Really liked your videos they are very easy to understand as compared to other tutorials

nice content

So useful as usual!

@Computerix

2 ай бұрын

Thanks :)

Amazing explanation. Thanks a lot!

@Computerix

Ай бұрын

My pleasure !

amayzing brother, thanks a lot

I really like your video. Thanks

Thanks.

Awsome, thank you for your efforts.

@amrhussien4334

2 ай бұрын

How can I contact you. I want to discuss something.

@Computerix

2 ай бұрын

@@amrhussien4334 Here is my linkedin : www.linkedin.com/in/charbel-el-helou-6523a5200 Thanks for the feedback!

Excellent video. Thank you for your effort. is there a particular reason why you used a different package for refresh tokens, instead of using the jwt package here as well?

@Computerix

Ай бұрын

Since the refresh token is not a JSON Web Token but rather a random string, we used a random generator

thanks 😁

@Computerix

29 күн бұрын

You're very welcome!

The source code plz

Very helpful ! can you make a video about authorization (roles: admin, user.. )

@Computerix

29 күн бұрын

Yes, this is on my list :)

👏👏👏👏👏 Thanks for your video. Can I ask if is there anyway to declare a jwt service for global level and another one in Auth module scope, like: using it for refresh only?

@Computerix

2 ай бұрын

You're welcome! Yes, you can register another Jwt Module in the AuthModule with its own secret and config.. and it would work. However, be careful, your Auth guard will be using one of the two jwt services (Most probably the global one).. So you would need to find a way to dynamically use the correct secret key when verifying your tokens.. Now if you have the same secret for both modules, but you're using different config options such as expiry etc.. I don't think you would face any issues.. you could also override the default config used in the global jwt module, by simply assigning them explicitly such as : jwtService.verify(token, { ...override-config-here ...}, in case you don't want to register a second jwt module. I'm not sure why you would use the jwtService with the refresh however, as the refresh token is a long random string (rather than a Json Web Token) Hope my answer helps!

@quang.luu.179

2 ай бұрын

​@@Computerix Thanks for your reply! I know I can inject any configuration into the JWT service to achieve this. Just asking for another approach. Regarding refresh tokens, generally, I see two ways in other samples: * Using a random string like you suggested. * Using JWT format. ( I dont know why) Updated: Ah, I guess the jwt can take the advantage of expired date that encoded into the self token without query the db for persistent. I mostly saw it from microservice architecture where a gateway is kinda the first line of token validator,

@problemchild959

18 күн бұрын

​@@Computerix a lot of people use a jwt token as the refresh token so that it while lasting much longer (a week or so) still has an expire time. using a refresh token that never expires is considered a bad security practice by a lot of people/companies.

@Computerix

18 күн бұрын

@@problemchild959 Correct about the expiration. BUT, you don't need to have the refresh token as a JWT for it to have an expiry date. You can use a random long string, and use an expirationDate field that you check against whenever you're calling your refresh token API to refresh the tokens. If that field has a value date in the past (meaning it expired), you force the user to login again.

@sonzaii-x

10 күн бұрын

​​@@Computerix I think using jwt for refresh tokens is more secure since you can invalidate all refresh tokens by editing the refresh token secret

wtf, you update refresh token per request why????? also why you protected all routes instead of what you real needed, video is like 5/10. good start - bad finish

@Computerix

Ай бұрын

You misunderstood the point. I called the refresh token API multiple times on purpose to show the behaviour. Of course you shouldn't call it unless the access token expires -.- + We added the authGuard on the controller level to protect all routes, assuming this is our use case.