@@jgoebel yes right but for the purpose of security when sending passwords, its safer to send a JWT for frequent authorizations because the password is generally not part of the claim even if someone DID decrypt it. With HTTPS and tls (version 1.2 I think?) there is always encryption for the data sent from client to server side and decryption is very difficult since it requires 2 private 🔑 and a public 🔑 So with a JWT sent via HTTPS, are you not sending hashed data that has already been encrypted?
Thank you for the JWT tip and thanks for all your videos!
thx, you're welcome!
Thanks for all your JWT stuffs. Awesome explanation👏
My pleasure!
Hey there , thanks for the vid! What is your opinion on whether JWT's are necessary when you're already using HTTPS / TLS ?
I am not sure I understand what you mean. https and JWTs are completely different things
@@jgoebel yes right but for the purpose of security when sending passwords, its safer to send a JWT for frequent authorizations because the password is generally not part of the claim even if someone DID decrypt it. With HTTPS and tls (version 1.2 I think?) there is always encryption for the data sent from client to server side and decryption is very difficult since it requires 2 private 🔑 and a public 🔑
So with a JWT sent via HTTPS, are you not sending hashed data that has already been encrypted?