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

Protecting API keys and secrets

1m:42s

You need to keep API Keys and API Secrets protected.

If they’re leaked:

  • You may incur huge fees
  • Your database may become corrupted and unusable

Neither is fun.

Once, I incurred a $60,000 expense on my Amazon account because my friend leaked my API Key and Secret. Thankfully, Amazon decided to waive that off or I would have been in deep trouble.

How to protect API Keys and API Secrets

There’s an industry-standard way to protect API Keys and API Secrets.

It involves two steps:

  1. Write the API Key and API secret in a .env file
  2. Gitignore the .env file

Let’s see how this is done.

Step 1: Using a .env file

First, you need to create a .env file and place it in your project’s root folder.

In this .env file, you can include any number of entries. Each entry should have the following syntax:

Terminal window
KEY_NAME="Your API Key"
SECRET_NAME="Your API Secret"
Note

We normally write keys and secrets in UPPER_CASE to denote them as constants (that will not be changed). This is a convention you can ignore if you wish to.

Getting keys from the .env file

You can extract values from this .env file with a package called dotenv.

You can install dotenv with the following command:

Terminal window
npm install dotenv -S

Once you have installed dotenv, write the following line in your server.js file.

import 'dotenv/config'

You can now use the variables you wrote in .env like this:

const YOUR_KEY = process.env.KEY_NAME
const YOUR_SECRET = process.env.SECRET_NAME
console.log(YOUR_KEY)
console.log(YOUR_SECRET)

Step 2: Gitignore the .env file

The second step is to gitignore the env file.

You can do this by creating a .gitignore file if it doesn’t exist already.

Then you insert .env into this gitignore file.

.env

That’s it!

Now we’re ready to move on to the next chapter, where you’ll learn everything you need to build a simple server with Express.