Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Understanding Async JS
Lesson Plan
  1. Introduction
    1. What is Asynchronous JS?
    2. Callbacks are not automatically asynchronous
    3. What is an API?
    4. Evolution of HTTP APIs
    5. Ajax vs Asynchronous JavaScript
  2. Fundamental Concepts
    1. How to fetch resources
    2. Using XHR
    3. Using the Fetch API
    4. Using libraries
    5. Core JavaScript concepts
    6. Understanding Promises
    7. Understanding Async Functions
    8. Understanding the Event Loop
    9. Understanding JSON
    10. Async JS Best Practices
    11. Using Optimistic UI
  3. Understanding Rest API
    1. Diving into Rest APIs
    2. The Rest Architecture
    3. The Rest Structure
    4. Anatomy of a Request
    5. What's an endpoint
    6. Request methods
    7. Understanding request headers
    8. Understanding the request body
    9. Authentication
    10. Basic Authentication
    11. Bearer Authentication
    12. Authenticating with API keys and API Secrets
    13. Cross Origin Resource Sharing
    14. Anatomy of a response
    15. HTTP Statuses
    16. Response headers
    17. The response body
    18. Handling Errors
    19. Reading API documentations
    20. Understanding Curl
  4. Node Basics
    1. Why we are using Node
    2. Command Line Basics
    3. Installing Node
    4. Managing dependencies
    5. Using ES Modules in Node
    6. Using Node
    7. Restarting the server automatically
    8. Sending requests via Node
    9. Protecting API keys and secrets
  5. Building a server
    1. What's a server
    2. Building a simple server with Express
    3. Two kinds of servers
    4. API Server architecture
    5. Handling routes
    6. Understanding Middlewares
    7. Enabling CORS
    8. Receiving data
    9. Sending responses
    10. Handling errors in Express
    11. Using the server as a proxy
    12. Minimum viable server
  6. Open Authorization
    1. Open Authorisation (OAuth)
    2. Authenticating with Access Tokens
    3. Obtaining Access Tokens
    4. Public and Confidential Clients
    5. Authorisation Code Grant
    6. Understanding scope
    7. Proof Key for Code Exchange (PKCE)
    8. PKCE with Twitter
    9. Dynamic state and `code_verifier`
    10. Saving the access token in cookies
    11. Passing access tokens to the browser
    12. Saving the access token in local storage
    13. Refresh Token Grant
    14. Device Code Grant
    15. Client libraries vs REST
  7. Building Social Media Logins
    1. Introduction
    2. Starter Files
    3. Creating SSL certificates
    4. Login in with Github
    5. Github: Saving the token to local storage
    6. Github: Persisting the login status
    7. Login with Twitter
    8. Twitter: Saving the token to local storage
    9. Twitter: Persisting the login status
    10. Twitter: Refreshing the access token
    11. Login with Facebook
    12. Facebook: Saving the token to localStorage
    13. Facebook: Persisting the login status
    14. Facebook: Refreshing the access token
    15. Login with google
    16. Google: Saving the token to localStorage
    17. Google: Refreshing the access token

Login in with Github

We let users login with Github first because it’s something we already know how to.

There are four steps:

  1. Create the app
  2. Create the sign-in link
  3. User logs in on Github
  4. Exchange code for access token

Create the app

We’re going to create an app on Github. Here are the instructions from Github on how to do this.

You can name the app anything you want.

  • I named it Social Media Login App.
  • We’re going to set callbackURL to https://auth/github/callback.
Creating a Github application
Note

Pay attention to the https protocol. Make sure you use https instead of http for this app.

We need this https protocol because we served this app with https.

Before you move on, make sure you add your Github credentials to the .env file.

Terminal window
GITHUB_CLIENT_ID="Your Client ID"
GITHUB_CLIENT_SECRET="Your Client Secret"

When the user clicks the sign-in link, we will redirect the user to Github. We can do this in two steps:

  1. We direct the user to an endpoint in our server.
  2. In this endpoint, we redirect the user to Github.
<!-- Direct user to endpoint in our server -->
<a href="/auth/github" ...> Login with Github </a>

In this endpoint, we craft the sign-in link and redirect the user to Github.

router.get('/auth/github', (req, res) => {
const baseURL = 'https://github.com/login/oauth/authorize'
const params = {
client_id: process.env.GITHUB_CLIENT_ID,
}
const query = new URLSearchParams(params)
const link = baseURL + '?' + query.toString()
return link
})

User logs in to Github

There’s nothing for us to do here :)

Exchange code for access token

Github will redirect the user to our callback url (/auth/github/callback) after they have logged in on Github. This callback url will contain a code query paramater.

We need to use this code value to get an access token.

We can grab the code value from the url through req.query.

router.get('/auth/github/callback', async (req, res) => {
const { code } = req.query
})

Then we send this code to Github’s token endpoint to get the access token.

router.get('/auth/github/callback', async (req, res) => {
// Exchange code for access token
const response = await zlFetch.post(
'https://github.com/login/oauth/access_token',
{
body: {
client_id: process.env.GITHUB_CLIENT_ID,
client_secret: process.env.GITHUB_CLIENT_SECRET,
code,
},
},
)
// Get the token
const token = response.body
console.log(token)
})

You should receive a token like this:

Picture of the token

The user is now logged in.

Handling the access token

We can save the access token in three places:

  1. A database
  2. Local storage
  3. Cookies

We’re going to store the access token in local storage for this app. We do this because of these three reasons:

  1. Local storage is easier to understand for frontend developers (like us).
  2. Local storage and cookies work the same way. They’re just saved in different places, which means the implementation is similar. Once you know how to use one, you’ll know how to use the other one.
  3. If you want to use cookies, you need to know how to use template engines on the server. We did not cover this in the course so it’s harder to explain how to use cookies.
Note

When you build a real application, make sure you always store the access token in your database. You want to do this because you can use it to verify the access token. More on this in a later lesson.

That’s it for this lesson. Let’s move on to the next one.