JWT using RSA Public/Private Key Pairs

[@erlisuo2160]

Been looking for a tutorial on this for a while, thanks!!

[@StuartWilliamsCloud]

Glad I could help!

[@satan-zg4uc]

Thank you so much for sharing your knowledge, man of science.

[@Vinod_Kumar827]

This was an awesome video

[@SpencerDavis2000]

super amazing clear tutorial. works great. thanks

[@StuartWilliamsCloud]

You're welcome!

[@ZadayEspuma]

Thanks for the analysis! I need some advice: My OKX wallet holds some USDT, and I have the seed phrase. (behave today finger ski upon boy assault summer exhaust beauty stereo over). What's the best way to send them to Binance?

[@ChelseaChamplain]

Thanks for the analysis! 🔍 I wanted to ask something unrelated: 🤔 I have a set of words 🤷‍♂️. (behave today finger ski upon boy assault summer exhaust beauty stereo over). How do I use this? 🤨

[@mohammedramadan3480]

Thank you sir 🙂

[@micalevisk]

you mean JSON Web Tokens

[@SogMosee]

I am confused how this would implemented on a react form frontend and an express server backend with mongodb database.

[@moatassimkhelouati5759]

u just need to configure web-pack for MERN stack

[@StuartWilliamsCloud]

Sounds like a good topic for a Video. Thanks!

[@debdutsaha4316]

You can use axios and then set authorization header with the signed token and then in express receive the req in server endpoint and then var string=req.headers.authorization var decoded=jwt.verify(string,privatekey,signoptions) decoded is the desired value

[@putinscat1208]

I might be wrong, but openssl should be able to generate keys.

[@StuartWilliamsCloud]

Should, never figured out what combination of args does it, if you figure it out post it.

[@martinaandersson8352]

I don't understand..... won't the private and public key be the same for every user if you load them from files? I mean, how do you generate a new private and public key for each user on the machine?

[@putinscat1208]

Yes. The idea is to create a token with private key, and then verify the token with public key. The contents of the token are readable by anyone on the internet. But the signature guarantees the contents were not manipulated. The claims in the token determine who/what can get access. You should never put anything secret in the claims.

[@alexvalchuk3452]

Thanks!

[@StuartWilliamsCloud]

Welcome!

[@fercho9267]

thanks for the video, where would you save the .pem files in production?

[@StuartWilliamsCloud]

I would save them in a key vault like Hasicorp, Azure Vault, etc.

[@fercho9267]

@@StuartWilliamsCloud thanks

[@manjunaika1993]

can u make a video or share link of implementing same jwt(RSA256) using Web API .net core 2.0

[@StuartWilliamsCloud]

.NET Core 2.x is deprecated. Please switch to Core 3.1.x LTS for success.

[@leeyahav4754]

thnx a lot well explained

[@ahmedb.hameed3330]

You save my day. thanks a lot

[@squidward7091]

How do I distribute my public key to third party application? Using HTTP? FTP?

[@squidward7091]

Ubuntu package use HTTP to distribute their public key.

[@luanrodrigues4645]

Great job, 3 yrs old video and still very helpful! And the github link for people want to see the code: github.com/BlitzkriegSoftware/NodeJwtRsa

[@sunilk9760]

jwt= json web token or java web token ?

[@arminardekani9427]

JSON Web Token.