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

Facebook: Saving the token to localStorage

Before we can save the token to Local Storage, we need to send the token to the browser.

We’re going to use the query string method to stay consistent with the apps we’ve created so far.

Sending token to frontend via the query string

Let’s take a look at the token Facebook sends back to us and see what values we need to send to our frontend.

We can see that expires_in is 5183280 minutes.

  • This means the access token will expire in 1439.8 hours. (Divide it by 3600).
  • It further means the access token will expire in 59.99 days. (Further divide it by 24).

Pretty cool! Facebook has given us a pretty long-lived access token and we don’t have to worry about refreshing the token for 60 days!

But it still expires… so we still need to create an expiresAt value and send it to the frontend. After all, we want to allow users to login to our app for longer than 60 days, don’t we?

const expiresAt = token.expires_in * 1000 + Date.now()

So with everything we’ve seen so far, we know we need to send four values to the frontend.

  1. authStatus
  2. provider
  3. access_token
  4. expiresAt

Here’s how you can do this.

router.get('/auth/github/callback', async (req, res) => {
// ...
const token = response.body
const expiresAt = token.expires_in * 1000 + Date.now()
// Sends the token to the browser to be stored in Local Storage
const params = {
authStatus: 'success',
provider: 'facebook',
expiresAt,
access_token: token.access_token,
}
const query = new URLSearchParams(params).toString()
res.redirect('/' + '?' + query)
})

Getting and saving the token

The code we have written so far already gets and saves the token values. So there’s nothing we have to do here!

If you look at your local storage, you should be able to see the access token from Facebook.

Let’s move on.