Web Authentication Methods Explained
Вставка
- Опубліковано 8 лип 2024
- Try out Frontegg: bit.ly/3uuzqEp
======⚡⚡⚡======
How does Authentication on the Web work? And what types of Authentication are available to Web Developers? In this video, we are going to explore methods such as Web Authentication API aka WebAuthn, Multi-Factor Authentication, Authentication with JWT or Cookies, Passwordless Authentication, and so on with thorough explanations.
🙌 Become my Patreon and get exclusive perks: / softdevdiaries
💼 Follow me on LinkedIn and drop me a message if you'd like: / gusgadirov
💻 Also, let's connect on GitHub: github.com/gusgad
🕒 Timestamps:
(00:00) Types of Authentication
(00:49) Cookies
(02:05) JWT
(02:41) Single Sign-On
(04:37) Multi-Factor Authentication
(05:30) Passwordless Authentication
(06:33) Biometric with Web Authentication API (WebAuthn)
(08:29) Frontegg
And don't forget to subscribe for more videos like this 😊 - Наука та технологія
Hey guys, let me know if I should make a dedicated video about one of these methods ✌️
Hey, a dedicated video on single-sign-on will be appreciated. thanks.
One about WebAuthn, detailing the data flow, would be great. Great presentation!
Will do!
You can't believe it, i was waiting for this.
Perfect timing 😀👌
My hero!!! men, so good
Very good video, thanks!
Thank you, appreciate it 😊
This is so concise and beautiful put together.
This video is super helpful! I am working on a research paper related to authentication methods and your explanation is to the point which really helps so thank you
Happy to hear mate! Best of luck with the paper
Excellent descripción, thanks a lot
Are there any books or courses to learn HOW to implement (best practices) each of these methods?
Not that I know of. Would suggest to simply research each of them by googling and reading on different websites :)
Cookie IDs are sent back to the server on subsequent requests … and you said JWTs are sent back to the server on subsequent requests. Where is the difference? How’s a cookie ID verified differently than a JWT?
Great point, thanks for the remark. I would suggest reading the 1st and 2nd answers from this post, I hope they'll answer your question:
stackoverflow.com/questions/37582444/jwt-vs-cookies-for-token-based-authentication
After studying the topic for months now, i have to say that there is way too much missing/misleading info on oauth/oidc and tokens for mention them all. I understand that the topic is way bigger than a few minutes of plug around an advertisement, but still...
just to not be a Debbie Downer, i highly recommend Philippe De Ryck's explanations on the topic, for example ua-cam.com/video/ZuQoN2x8T6k/v-deo.html
Don't y'all think Frontegg is a little expensive.
No cons with OAuth?? Really??? 🤣🤣🤣
🤍🍻