AUTH_TOKEN

Your authentication token that you acquired after a successful login.

GMAIL_EMAIL

Your email on Gmail that will be used to send confirmation emails.

OAUTH_CLIENT_ID

Your client id that we explained in the Secure Emails lesson.

OAUTH_CLIENT_SECRET

Your client's secret that we explained in the Secure Emails lesson.

OAUTH_REFRESH_TOKEN

Your refresh token that we explained in the Secure Emails lesson.

docker.tar.gz

PORT

CONFIRMATION_SECRET_KEY

CRYPTO_ALGORITHM

INITIALIZATION_VECTOR

MONGO_URI

SALT

TOKEN_SECRET_KEY

hello_world

wrong_hello_world

routes_examples

events

async

mongoose

usermodel

signup

confirmation

login

auth

props

router

react

SignupGUI

ConfirmationGUI

LoginGUI

AuthGUI

navbar

SignupPage

SignupPageGUI

ConfirmationPage

LoginPage

ux-page

home-page

UploadGUI

SpellGUI

ImageGUI

GetGUI

UpdateGUI

DeleteGUI

CRUD

Heroku

GetGUI-copy

SpellGUIV2

ImageGUIV2

CRUDV2

Node.js is a popular JavaScript runtime environment used to create server-side applications. It is an ideal tool for building robust, full-stack web applications with React.

This course is an introduction to web development leveraging these two popular technologies. You’ll learn server-side applications with Node.js and learn to add database functionality with MongoDB fitting into the Express application framework. You’ll then build a user authorization system using the JSON Web Token (JWT).

You’ll then focus on a client-side environment built with React. You’ll build a sample application to get familiar with the framework before styling the application and adding necessary user-interaction elements. You’ll wrap up by tying the frontend and backend together and deploying your web application with Heroku.

By the end of this course, you’ll be prepared to build real-world websites using the most popular JavaScript tools.

Building Full-Stack Web Applications With Node.js and React

JWT makes it possible to communicate securely between two sides.

**(Select all that apply.)** Which statement is true about JWT? 


(Select all that apply.) Which statement is true about JWT?

```
const token = jwt.sign({email:'user@educative.com'}, "Stack", { expiresIn: "1000000h" });
```

```
const token = jwt.sign({email:'user@educative.com'}, "Stack", { expiresIn: "1000000d" });
```

```
const token = jwt.sign({email:'user@educative.com'}, "Stack", { expiresIn: "1000000s" });
```

```
const token = jwt.sign({email:'user@educative.com'}, "Stack", {});
```

What code sets the JWT token expiration time to the maximum possible time?

What code sets the JWT token expiration time to the maximum possible time?

```
const signature = token.split(".")[0]
```

```
const signature = token.split(".")[1]
```

```
const signature = token.split(".")[2]
```

```
const signature = token.split(".")[4]
```

In the following JWT token, how is the signature part extracted?

```
const token = eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6InVzZXIxIiwiZXhwIjoxNTQ3OTc0MDgyfQ.2Ye5_w1z3zpD4dSGdRp3s98ZipCNQqmsHRB9vioOx54
```

In the following JWT token, how is the signature part extracted?
<pre><code>const token = eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6InVzZXIxIiwiZXhwIjoxNTQ3OTc0MDgyfQ.2Ye5_w1z3zpD4dSGdRp3s98ZipCNQqmsHRB9vioOx54
</code></pre>

A synchronously signed token with RSA SHA256 algorithm.

An asynchronously signed token with an RSA SHA256 algorithm.

A synchronously signed token with an HMAC SHA256 algorithm.


An asynchronously signed token with an HMAC SHA256 algorithm.


What is the output of the following code?

```
jwt.sign({ foo: 'bar' }, privateKey, { algorithm: 'RS256' }, function(err, token) {
  console.log(token);
});
```

What is the output of the following code?
<pre><code>jwt.sign({ foo: 'bar' }, privateKey, { algorithm: 'RS256' }, function(err, token) {
 console.log(token);
});
</code></pre>

How are JWT Tokens destroyed at logout?

Before You Begin

The Server-side

User Authentication with a JSON Web Token

Set up the Client-side Environment

Develop the Client-side

Business Logic

Server-side Routes

Client-side Routes

Appendix

Conclusion

Test Yourself: JSON Web Tokens