Spring Boot Web Application, Study Guides, Projects, Research of Computer science

A complete introduction to Spring Boot Web Application

Typology: Study Guides, Projects, Research

2018/2019

Uploaded on 11/27/2019

grusso74
grusso74 🇮🇹

8 documents

1 / 11

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download Spring Boot Web Application and more Study Guides, Projects, Research Computer science in PDF only on Docsity!

Standard January 9, 2017 by jt 8 Comments This is the fifth part of my tutorial series on building a Spring Boot Web Application. We started off in the first part looking at using the Spring Initializr to start our Spring Boot project. In part 2, we configured Spring MVC and ThymeLeaf templates to display a basic web page. This was followed by part 3 where we setup the H2 database and Spring Data JPA and used them to persist data of our application to the database. In part 4, we consolidated everything to provide a working Spring Boot MVC Web Application capable of performing CRUD operations. We now have an application which displays data from the database, allows you to create new records, update existing records, and delete selected records too. In part 5, we will use Spring Security to set up authentication and authorization in our application. Spring Security, one of the most commonly used project in the Spring family of projects, provides a powerful and highly customizable authentication and authorization framework designed specifically to secure Java applications. In this part, I'll show you how to setup Spring Security to secure our Spring Boot Web Application using the basic in-memory authentication provider. Security Requirements Our Spring Boot Web application in the current state is accessible to all users. Any user can create and view products, and also edit or delete them. Before we setup Spring Security to secure our application, let's set few security requirements: e An anonymous user (user who doesn’t sign in) should be able to view the home page and product listing. e An authenticated user, in addition to the home page and product listing, should be able to view the details of a product. « An authenticated admin user, in addition to the above, should be able to create, update, and delete products. Maven Dependencies Spring Security is already listed as a dependency of our application in the Maven POM. In the Maven Projects pane of IntelliJ we can see the additional dependencies of Spring Security. | Maven Projects - +1 | fx JL 5 iL, -_ IK a