Refactor an existing authentication project by using cookies and JSON Web Token to increase security. Cookies are a way for a browser to store information while tokens are a stand-in or representation for something else.
Overview
Syllabus
Cookies
Cookies are a way for a browser to store information. This can be anything from a language preference to how a visitor found about a site. Cookies are used on any type of site, even ones that don't use authentication.
Chevron 12 steps-
Securing Browser Information
3:21
-
Cookies vs Session Storage
3:04
-
Secure Browsing
5 questions
-
Creating a Cookie
3:42
-
Storing and Retrieving Cookies
3:57
-
Working with Cookies
2 objectives
-
Cookie Settings
2:11
-
Managing Cookies
6:27
-
Managing Cookie Settings
5 questions
-
Decoding Cookies
3:09
-
Using Cookies for Authentication
3:01
-
Cookies
5 questions
JSON Web Tokens
Tokens are a stand-in or representation for something else. In the real world, this may be a key card that lets you access a building, or a wedding ring that represents your vows. Both of these are a type of token.
Chevron 7 steps-
JSON Web Tokens
2:13
-
Setting up the Packages
4:55
-
Working with JWT
5 questions
-
Building a JWT
2:49
-
Decoding a JWT
3:27
-
The Continuing Journey
1:34
-
JSON Web Tokens
7 questions