Book Image

Building Applications with Spring 5 and Vue.js 2

By : James J. Ye
Book Image

Building Applications with Spring 5 and Vue.js 2

By: James J. Ye

Overview of this book

Building Applications with Spring 5 and Vue.js 2, with its practical approach, helps you become a full-stack web developer. As well as knowing how to write frontend and backend code, a developer has to tackle all problems encountered in the application development life cycle – starting from the simple idea of an application, to the UI and technical designs, and all the way to implementation, testing, production deployment, and monitoring. With the help of this book, you'll get to grips with Spring 5 and Vue.js 2 as you learn how to develop a web application. From the initial structuring to full deployment, you’ll be guided at every step of developing a web application from scratch with Vue.js 2 and Spring 5. You’ll learn how to create different components of your application as you progress through each chapter, followed by exploring different tools in these frameworks to expedite your development cycle. By the end of this book, you’ll have gained a complete understanding of the key design patterns and best practices that underpin professional full-stack web development.
Table of Contents (23 chapters)
Title Page
Copyright and Credits
Dedication
About Packt
Contributors
Preface
Index

How to secure a web application


Security is a very broad topic and it covers many aspects. Due to the scope of this book, we will mainly focus on the security that a web application needs to take care of, which includes authentication, authorization, and preventing attacks such as Cross-Site Scripting (XSS) and SQL/NoSQL injection. Topics such as how to secure a server or how to prevent a distributed denial-of-service (DDoS) attack will not be covered here. 

So, how do we secure a web application? It really comes down to three aspects:

  • Authenticating users
  • Authorizing users
  • Preventing attacks

Let's take TaskAgile as an example. We want only those users that we have authenticated to access the application. So, people will need to log in to the application before using it, except the register and the login page, which are accessible publicly. We also want to limit the resources that authenticated users can access to only those that they have been authorized for. For example, they should not be...