Packt+ | Advance your knowledge in tech

You're reading from Building Enterprise JavaScript Applications Learn to build and deploy robust JavaScript applications using Cucumber, Mocha, Jenkins, Docker, and Kubernetes

Product type Paperback

Published in Sep 2018

Publisher Packt

ISBN-13 9781788477321

Length 764 pages

Edition 1st Edition

Languages

JavaScript

Tools

Cucumber

Concepts

Application Development

Author (1):

Daniel Li

View More author details

Table of Contents (26) Chapters

Title Page

Dedication

Packt Upsell

Contributors

Preface

1. The Importance of Good Code FREE CHAPTER

2. The State of JavaScript

3. Managing Version History with Git

4. Setting Up Development Tools

5. Writing End-to-End Tests

6. Storing Data in Elasticsearch

7. Modularizing Our Code

8. Writing Unit/Integration Tests

9. Designing Our API

10. Deploying Our Application on a VPS

11. Continuous Integration

12. Security – Authentication and Authorization

13. Documenting Our API

14. Creating UI with React

15. E2E Testing in React

16. Managing States with Redux

17. Migrating to Docker

18. Robust Infrastructure with Kubernetes

1. Other Books You May Enjoy

Leave a review - let other readers know what you think

Index

Chapter 12. Security – Authentication and Authorization

So far in this book, we have developed a simple API that allows anonymous users to create, retrieve, modify, and delete users. This is insecure and impractical for any real-world applications. Therefore, in this chapter, we will begin to secure our API by implementing a rudimentary authentication and authorization layer on top of it. This will also give us a chance to practice the TDD process and work with the CI servers.

The purpose of this chapter is to show you how to implement a stateless authentication and authorization scheme using JSON Web Tokens (JWTs). Being stateless is extremely important to ensure the scalability of our application, something which we will discuss in Chapter 18, Robust Infrastructure with Kubernetes.

By the end of this chapter, our API will be more secure than its current state, but there'll still be a lot more steps we need to take to truly secure it. It'll be impossible to cover all security-related topics...