Securing a Web Application

This guide walks you through the process of creating a simple web application with resources that are protected by Spring Security.

What You Will Build

You will build a Spring MVC application that secures the page with a login form that is backed by a fixed list of users.

What You Need

• About 15 minutes
• A favorite text editor or IDE
• Java 17 or later
• Gradle 7.5+ or Maven 3.5+
• You can also import the code straight into your IDE:

How to complete this guide

Like most Spring Getting Started guides, you can start from scratch and complete each step or you can bypass basic setup steps that are already familiar to you. Either way, you end up with working code.

To start from scratch, move on to Starting with Spring Initializr.

To skip the basics, do the following:

• Download and unzip the source repository for this guide, or clone it using Git: git clone https://github.com/spring-guides/gs-securing-web.git
• cd into gs-securing-web/initial
• Jump ahead to Create an Unsecured Web Application.

When you finish, you can check your results against the code in gs-securing-web/complete .

Starting with Spring Initializr

You can use this pre-initialized project and click Generate to download a ZIP file. This project is configured to fit the examples in this tutorial.

To manually initialize the project:

1. Navigate to https://start.spring.io. This service pulls in all the dependencies you need for an application and does most of the setup for you.
2. Choose either Gradle or Maven and the language you want to use. This guide assumes that you chose Java.
3. Click Dependencies and select Spring Web and Thymeleaf.
4. Click Generate.
5. Download the resulting ZIP file, which is an archive of a web application that is configured with your choices.

Create an Unsecured Web Application

Before you can apply security to a web application, you need a web application to secure. This section walks you through creating a simple web application. Then you will secure it with Spring Security in the next section.

The web application includes two simple views: a home page and a “Hello, World” page. The home page is defined in the following Thymeleaf template (from src/main/resources/templates/home.html ):

     
Welcome!
 
Click ">here to see a greeting.
  

This simple view includes a link to the /hello page, which is defined in the following Thymeleaf template (from src/main/resources/templates/hello.html ):

The web application is based on Spring MVC. As a result, you need to configure Spring MVC and set up view controllers to expose these templates. The following listing (from src/main/java/com/example/securingweb/MvcConfig.java ) shows a class that configures Spring MVC in the application:

package com.example.securingweb; import org.springframework.context.annotation.Configuration; import org.springframework.web.servlet.config.annotation.ViewControllerRegistry; import org.springframework.web.servlet.config.annotation.WebMvcConfigurer; @Configuration public class MvcConfig implements WebMvcConfigurer < public void addViewControllers(ViewControllerRegistry registry) < registry.addViewController("/home").setViewName("home"); registry.addViewController("/").setViewName("home"); registry.addViewController("/hello").setViewName("hello"); registry.addViewController("/login").setViewName("login"); >>

The addViewControllers() method (which overrides the method of the same name in WebMvcConfigurer ) adds four view controllers. Two of the view controllers reference the view whose name is home (defined in home.html ), and another references the view named hello (defined in hello.html ). The fourth view controller references another view named login . You will create that view in the next section.

At this point, you could jump ahead to “Run the Application” and run the application without having to log in to anything.

Now that you have an unsecured web application, you can add security to it.

Set up Spring Security

Suppose that you want to prevent unauthorized users from viewing the greeting page at /hello . As it is now, if visitors click the link on the home page, they see the greeting with no barriers to stop them. You need to add a barrier that forces the visitor to sign in before they can see that page.

You do that by configuring Spring Security in the application. If Spring Security is on the classpath, Spring Boot automatically secures all HTTP endpoints with “basic” authentication. However, you can further customize the security settings. The first thing you need to do is add Spring Security to the classpath.

With Gradle, you need to add three lines (one for the application, one for Thymeleaf & Spring Security integration, and one for testing) in the dependencies closure in build.gradle , as the following listing shows:

implementation 'org.springframework.boot:spring-boot-starter-security' // Temporary explicit version to fix Thymeleaf bug implementation 'org.thymeleaf.extras:thymeleaf-extras-springsecurity6:3.1.1.RELEASE' implementation 'org.springframework.security:spring-security-test'

The following listing shows the finished build.gradle file:

plugins < id 'java' id 'org.springframework.boot' version '3.1.0' id 'io.spring.dependency-management' version '1.1.0' >group = 'com.example' version = '0.0.1-SNAPSHOT' sourceCompatibility = '17' repositories < mavenCentral() >dependencies < implementation 'org.springframework.boot:spring-boot-starter-web' implementation 'org.springframework.boot:spring-boot-starter-thymeleaf' implementation 'org.springframework.boot:spring-boot-starter-security' // Temporary explicit version to fix Thymeleaf bug implementation 'org.thymeleaf.extras:thymeleaf-extras-springsecurity6:3.1.1.RELEASE' implementation 'org.springframework.security:spring-security-test' testImplementation 'org.springframework.boot:spring-boot-starter-test' >test

With Maven, you need to add two extra entries (one for the application and one for testing) to the element in pom.xml , as the following listing shows:

 org.springframework.boot spring-boot-starter-security  org.thymeleaf.extras thymeleaf-extras-springsecurity6 3.1.1.RELEASE  org.springframework.security spring-security-test test 

The following listing shows the finished pom.xml file:

  4.0.0 org.springframework.boot spring-boot-starter-parent 3.1.0 com.example securing-web-complete 0.0.1-SNAPSHOT securing-web-complete Demo project for Spring Boot 17   org.springframework.boot spring-boot-starter-thymeleaf  org.springframework.boot spring-boot-starter-web  org.springframework.boot spring-boot-starter-security  org.thymeleaf.extras thymeleaf-extras-springsecurity6 3.1.1.RELEASE  org.springframework.security spring-security-test test  org.springframework.boot spring-boot-starter-test test   

The following security configuration (from src/main/java/com/example/securingweb/WebSecurityConfig.java ) ensures that only authenticated users can see the secret greeting:

package com.example.securingweb; import org.springframework.context.annotation.Bean; import org.springframework.context.annotation.Configuration; import org.springframework.security.config.annotation.web.builders.HttpSecurity; import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity; import org.springframework.security.core.userdetails.User; import org.springframework.security.core.userdetails.UserDetails; import org.springframework.security.core.userdetails.UserDetailsService; import org.springframework.security.provisioning.InMemoryUserDetailsManager; import org.springframework.security.web.SecurityFilterChain; @Configuration @EnableWebSecurity public class WebSecurityConfig < @Bean public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception < http .authorizeHttpRequests((requests) ->requests .requestMatchers("/", "/home").permitAll() .anyRequest().authenticated() ) .formLogin((form) -> form .loginPage("/login") .permitAll() ) .logout((logout) -> logout.permitAll()); return http.build(); > @Bean public UserDetailsService userDetailsService() < UserDetails user = User.withDefaultPasswordEncoder() .username("user") .password("password") .roles("USER") .build(); return new InMemoryUserDetailsManager(user); >>

The WebSecurityConfig class is annotated with @EnableWebSecurity to enable Spring Security’s web security support and provide the Spring MVC integration. It also exposes two beans to set some specifics for the web security configuration:

The SecurityFilterChain bean defines which URL paths should be secured and which should not. Specifically, the / and /home paths are configured to not require any authentication. All other paths must be authenticated.

When a user successfully logs in, they are redirected to the previously requested page that required authentication. There is a custom /login page (which is specified by loginPage() ), and everyone is allowed to view it.

The UserDetailsService bean sets up an in-memory user store with a single user. That user is given a user name of user , a password of password , and a role of USER .

Now you need to create the login page. There is already a view controller for the login view, so you need only to create the login view itself, as the following listing (from src/main/resources/templates/login.html ) shows:

     
 Invalid username and password.
 
 You have been logged out.
 
 
 User Name : 
 
 Password: 
 
 
  

This Thymeleaf template presents a form that captures a username and password and posts them to /login . As configured, Spring Security provides a filter that intercepts that request and authenticates the user. If the user fails to authenticate, the page is redirected to /login?error , and your page displays the appropriate error message. Upon successfully signing out, your application is sent to /login?logout , and your page displays the appropriate success message.

Last, you need to provide the visitor a way to display the current user name and sign out. To do so, update the hello.html to say hello to the current user and contain a Sign Out form, as the following listing (from src/main/resources/templates/hello.html ) shows:

     
Hello thymeleaf!
 
 
  

We display the username by using Thymeleaf’s integration with Spring Security. The “Sign Out” form submits a POST to /logout . Upon successfully logging out, it redirects the user to /login?logout .

Thymeleaf 3.1 no longer provides access to HttpServletRequest so HttpServletRequest#getRemoteUser() cannot be used to access the currently authenticated user.

Run the Application

The Spring Initializr creates an application class for you. In this case, you need not modify the class. The following listing (from src/main/java/com/example/securingweb/SecuringWebApplication.java ) shows the application class:

package com.example.securingweb; import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; @SpringBootApplication public class SecuringWebApplication < public static void main(String[] args) throws Throwable < SpringApplication.run(SecuringWebApplication.class, args); >>

Build an executable JAR

You can run the application from the command line with Gradle or Maven. You can also build a single executable JAR file that contains all the necessary dependencies, classes, and resources and run that. Building an executable jar makes it easy to ship, version, and deploy the service as an application throughout the development lifecycle, across different environments, and so forth.

If you use Gradle, you can run the application by using ./gradlew bootRun . Alternatively, you can build the JAR file by using ./gradlew build and then run the JAR file, as follows:

java -jar build/libs/gs-securing-web-0.1.0.jar

If you use Maven, you can run the application by using ./mvnw spring-boot:run . Alternatively, you can build the JAR file with ./mvnw clean package and then run the JAR file, as follows:

java -jar target/gs-securing-web-0.1.0.jar

Once the application starts up, point your browser to http://localhost:8080 . You should see the home page, as the following image shows:

When you click on the link, it attempts to take you to the greeting page at /hello . However, because that page is secured and you have not yet logged in, it takes you to the login page, as the following image shows:

If you jumped down here with the unsecured version, you do not see the login page. You should back up and write the rest of the security-based code.

At the login page, sign in as the test user by entering user and password for the username and password fields, respectively. Once you submit the login form, you are authenticated and then taken to the greeting page, as the following image shows:

If you click on the Sign Out button, your authentication is revoked, and you are returned to the login page with a message indicating that you are logged out.

Summary

Congratulations! You have developed a simple web application that is secured with Spring Security.

See Also

The following guides may also be helpful:

Want to write a new guide or contribute to an existing one? Check out our contribution guidelines.

Источник