此版本仍在开发中，尚未被视为稳定版本。对于最新的稳定版本，请使用 Spring Security 6.4.5！spring-doc.cadn.net.cn

Java 配置

在 Spring 3.1 中，Spring Framework 中添加了对 Java 配置的一般支持。 Spring Security 3.2 引入了 Java 配置，允许用户在不使用任何 XML 的情况下配置 Spring Security。spring-doc.cadn.net.cn

如果您熟悉 Security Namespace Configuration，您应该会发现它与 Spring Security Java 配置之间有很多相似之处。spring-doc.cadn.net.cn

Spring Security 提供了许多示例应用程序来演示 Spring Security Java Configuration 的使用。spring-doc.cadn.net.cn

Hello Web Security Java 配置

第一步是创建我们的 Spring Security Java 配置。该配置将创建一个称为springSecurityFilterChain，它负责应用程序中的所有安全性（保护应用程序 URL、验证提交的用户名和密码、重定向到登录表单等）。以下示例显示了 Spring Security Java 配置的最基本示例：spring-doc.cadn.net.cn

import org.springframework.beans.factory.annotation.Autowired;

import org.springframework.context.annotation.*;
import org.springframework.security.config.annotation.authentication.builders.*;
import org.springframework.security.config.annotation.web.configuration.*;

@Configuration
@EnableWebSecurity
public class WebSecurityConfig {

	@Bean
	public UserDetailsService userDetailsService() {
		InMemoryUserDetailsManager manager = new InMemoryUserDetailsManager();
		manager.createUser(User.withDefaultPasswordEncoder().username("user").password("password").roles("USER").build());
		return manager;
	}
}



This configuration is not complex or extensive, but it does a lot:spring-doc.cadn.net.cn




Require authentication to every URL in your applicationspring-doc.cadn.net.cn


Generate a login form for youspring-doc.cadn.net.cn


Let the user with a Username of user and a Password of password authenticate with form based authenticationspring-doc.cadn.net.cn


Let the user logoutspring-doc.cadn.net.cn


CSRF attack preventionspring-doc.cadn.net.cn


Session Fixation protectionspring-doc.cadn.net.cn


Security Header integration:spring-doc.cadn.net.cn



HTTP Strict Transport Security for secure requestsspring-doc.cadn.net.cn


X-Content-Type-Options integrationspring-doc.cadn.net.cn


Cache Control (which you can override later in your application to allow caching of your static resources)spring-doc.cadn.net.cn


X-XSS-Protection integrationspring-doc.cadn.net.cn


X-Frame-Options integration to help prevent Clickjackingspring-doc.cadn.net.cn





Integration with the following Servlet API methods:spring-doc.cadn.net.cn



HttpServletRequest#getRemoteUser()spring-doc.cadn.net.cn


HttpServletRequest#getUserPrincipal()spring-doc.cadn.net.cn


HttpServletRequest#isUserInRole(java.lang.String)spring-doc.cadn.net.cn


HttpServletRequest#login(java.lang.String, java.lang.String)spring-doc.cadn.net.cn


HttpServletRequest#logout()spring-doc.cadn.net.cn







AbstractSecurityWebApplicationInitializer

The next step is to register the springSecurityFilterChain with the WAR file.
You can do so in Java configuration with Spring’s WebApplicationInitializer support in a Servlet 3.0+ environment.
Not surprisingly, Spring Security provides a base class (AbstractSecurityWebApplicationInitializer) to ensure that the springSecurityFilterChain gets registered for you.
The way in which we use AbstractSecurityWebApplicationInitializer differs depending on if we are already using Spring or if Spring Security is the only Spring component in our application.spring-doc.cadn.net.cn




AbstractSecurityWebApplicationInitializer without Existing Spring - Use these instructions if you are not already using Springspring-doc.cadn.net.cn


AbstractSecurityWebApplicationInitializer with Spring MVC - Use these instructions if you are already using Springspring-doc.cadn.net.cn





AbstractSecurityWebApplicationInitializer without Existing Spring

If you are not using Spring or Spring MVC, you need to pass the WebSecurityConfig to the superclass to ensure the configuration is picked up:spring-doc.cadn.net.cn



import org.springframework.security.web.context.*;

public class SecurityWebApplicationInitializer
	extends AbstractSecurityWebApplicationInitializer {

	public SecurityWebApplicationInitializer() {
		super(WebSecurityConfig.class);
	}
}




The SecurityWebApplicationInitializer:spring-doc.cadn.net.cn




Automatically registers the springSecurityFilterChain Filter for every URL in your application.spring-doc.cadn.net.cn


Add a ContextLoaderListener that loads the WebSecurityConfig.spring-doc.cadn.net.cn





AbstractSecurityWebApplicationInitializer with Spring MVC

If we use Spring elsewhere in our application, we probably already have a WebApplicationInitializer that is loading our Spring Configuration.
If we use the previous configuration, we would get an error.
Instead, we should register Spring Security with the existing ApplicationContext.
For example, if we use Spring MVC, our SecurityWebApplicationInitializer could look something like the following:spring-doc.cadn.net.cn



import org.springframework.security.web.context.*;

public class SecurityWebApplicationInitializer
	extends AbstractSecurityWebApplicationInitializer {

}




This only registers the springSecurityFilterChain for every URL in your application.
After that, we need to ensure that WebSecurityConfig was loaded in our existing ApplicationInitializer.
For example, if we use Spring MVC it is added in the getServletConfigClasses():spring-doc.cadn.net.cn



public class MvcWebApplicationInitializer extends
		AbstractAnnotationConfigDispatcherServletInitializer {

	@Override
	protected Class<?>[] getServletConfigClasses() {
		return new Class[] { WebSecurityConfig.class, WebMvcConfig.class };
	}

	// ... other overrides ...
}



The reason for this is that Spring Security needs to be able to inspect some Spring MVC configuration in order to appropriately configure underlying request matchers, so they need to be in the same application context.
Placing Spring Security in getRootConfigClasses places it into a parent application context that may not be able to find Spring MVC’s HandlerMappingIntrospector.spring-doc.cadn.net.cn


Configuring for Multiple Spring MVC Dispatchers

If desired, any Spring Security configuration that is unrelated to Spring MVC may be placed in a different configuration class like so:spring-doc.cadn.net.cn



public class MvcWebApplicationInitializer extends
		AbstractAnnotationConfigDispatcherServletInitializer {

	@Override
    protected Class<?>[] getRootConfigClasses() {
		return new Class[] { NonWebSecurityConfig.class };
    }

	@Override
	protected Class<?>[] getServletConfigClasses() {
		return new Class[] { WebSecurityConfig.class, WebMvcConfig.class };
	}

	// ... other overrides ...
}



This can be helpful if you have multiple instances of AbstractAnnotationConfigDispatcherServletInitializer and don’t want to duplicate the general security configuration across both of them.spring-doc.cadn.net.cn



HttpSecurity


Thus far, our WebSecurityConfig contains only information about how to authenticate our users.
How does Spring Security know that we want to require all users to be authenticated?
How does Spring Security know we want to support form-based authentication?
Actually, there is a configuration class (called SecurityFilterChain) that is being invoked behind the scenes.
It is configured with the following default implementation:spring-doc.cadn.net.cn



@Bean
public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
	http
		.authorizeHttpRequests(authorize -> authorize
			.anyRequest().authenticated()
		)
		.formLogin(withDefaults())
		.httpBasic(withDefaults());
	return http.build();
}



The default configuration (shown in the preceding example):spring-doc.cadn.net.cn




Ensures that any request to our application requires the user to be authenticatedspring-doc.cadn.net.cn


Lets users authenticate with form based loginspring-doc.cadn.net.cn


Lets users authenticate with HTTP Basic authenticationspring-doc.cadn.net.cn




Note that this configuration is parallels the XML Namespace configuration:spring-doc.cadn.net.cn



<http>
	<intercept-url pattern="/**" access="authenticated"/>
	<form-login />
	<http-basic />
</http>





Multiple HttpSecurity Instances


We can configure multiple HttpSecurity instances just as we can have multiple <http> blocks in XML.
The key is to register multiple SecurityFilterChain @Beans.
The following example has a different configuration for URLs that start with /api/.spring-doc.cadn.net.cn



@Configuration
@EnableWebSecurity
public class MultiHttpSecurityConfig {
	@Bean                                                             (1)
	public UserDetailsService userDetailsService() throws Exception {
		// ensure the passwords are encoded properly
		UserBuilder users = User.withDefaultPasswordEncoder();
		InMemoryUserDetailsManager manager = new InMemoryUserDetailsManager();
		manager.createUser(users.username("user").password("password").roles("USER").build());
		manager.createUser(users.username("admin").password("password").roles("USER","ADMIN").build());
		return manager;
	}

	@Bean
	@Order(1)                                                        (2)
	public SecurityFilterChain apiFilterChain(HttpSecurity http) throws Exception {
		http
			.securityMatcher("/api/**")                              (3)
			.authorizeHttpRequests(authorize -> authorize
				.anyRequest().hasRole("ADMIN")
			)
			.httpBasic(withDefaults());
		return http.build();
	}

	@Bean                                                            (4)
	public SecurityFilterChain formLoginFilterChain(HttpSecurity http) throws Exception {
		http
			.authorizeHttpRequests(authorize -> authorize
				.anyRequest().authenticated()
			)
			.formLogin(withDefaults());
		return http.build();
	}
}





1
Configure Authentication as usual.


2
Create an instance of SecurityFilterChain that contains @Order to specify which SecurityFilterChain should be considered first.


3
The http.securityMatcher states that this HttpSecurity is applicable only to URLs that start with /api/.


4
Create another instance of SecurityFilterChain.
If the URL does not start with /api/, this configuration is used.
This configuration is considered after apiFilterChain, since it has an @Order value after 1 (no @Order defaults to last).






Custom DSLs


You can provide your own custom DSLs in Spring Security:spring-doc.cadn.net.cn






Javaspring-doc.cadn.net.cn


Kotlinspring-doc.cadn.net.cn






public class MyCustomDsl extends AbstractHttpConfigurer<MyCustomDsl, HttpSecurity> {
	private boolean flag;

	@Override
	public void init(HttpSecurity http) throws Exception {
		// any method that adds another configurer
		// must be done in the init method
		http.csrf().disable();
	}

	@Override
	public void configure(HttpSecurity http) throws Exception {
		ApplicationContext context = http.getSharedObject(ApplicationContext.class);

		// here we lookup from the ApplicationContext. You can also just create a new instance.
		MyFilter myFilter = context.getBean(MyFilter.class);
		myFilter.setFlag(flag);
		http.addFilterBefore(myFilter, UsernamePasswordAuthenticationFilter.class);
	}

	public MyCustomDsl flag(boolean value) {
		this.flag = value;
		return this;
	}

	public static MyCustomDsl customDsl() {
		return new MyCustomDsl();
	}
}






class MyCustomDsl : AbstractHttpConfigurer<MyCustomDsl, HttpSecurity>() {
    var flag: Boolean = false

    override fun init(http: HttpSecurity) {
        // any method that adds another configurer
        // must be done in the init method
        http.csrf().disable()
    }

    override fun configure(http: HttpSecurity) {
        val context: ApplicationContext = http.getSharedObject(ApplicationContext::class.java)

        // here we lookup from the ApplicationContext. You can also just create a new instance.
        val myFilter: MyFilter = context.getBean(MyFilter::class.java)
        myFilter.setFlag(flag)
        http.addFilterBefore(myFilter, UsernamePasswordAuthenticationFilter::class.java)
    }

    companion object {
        @JvmStatic
        fun customDsl(): MyCustomDsl {
            return MyCustomDsl()
        }
    }
}













This is actually how methods like HttpSecurity.authorizeHttpRequests() are implemented.spring-doc.cadn.net.cn






You can then use the custom DSL:spring-doc.cadn.net.cn






Javaspring-doc.cadn.net.cn


Kotlinspring-doc.cadn.net.cn






@Configuration
@EnableWebSecurity
public class Config {
	@Bean
	public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
		http
			.with(MyCustomDsl.customDsl(), (dsl) -> dsl
				.flag(true)
			)
			// ...
		return http.build();
	}
}






@Configuration
@EnableWebSecurity
class Config {

    @Bean
    fun filterChain(http: HttpSecurity): SecurityFilterChain {
        http
            .with(MyCustomDsl.customDsl()) {
                flag = true
            }
            // ...

        return http.build()
    }
}






The code is invoked in the following order:spring-doc.cadn.net.cn




Code in the Config.filterChain method is invokedspring-doc.cadn.net.cn


Code in the MyCustomDsl.init method is invokedspring-doc.cadn.net.cn


Code in the MyCustomDsl.configure method is invokedspring-doc.cadn.net.cn




If you want, you can have HttpSecurity add MyCustomDsl by default by using SpringFactories.
For example, you can create a resource on the classpath named META-INF/spring.factories with the following contents:spring-doc.cadn.net.cn


META-INF/spring.factories

org.springframework.security.config.annotation.web.configurers.AbstractHttpConfigurer = sample.MyCustomDsl



You can also explicit disable the default:spring-doc.cadn.net.cn






Javaspring-doc.cadn.net.cn


Kotlinspring-doc.cadn.net.cn






@Configuration
@EnableWebSecurity
public class Config {
	@Bean
	public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
		http
			.with(MyCustomDsl.customDsl(), (dsl) -> dsl
				.disable()
			)
			...;
		return http.build();
	}
}






@Configuration
@EnableWebSecurity
class Config {

    @Bean
    fun filterChain(http: HttpSecurity): SecurityFilterChain {
        http
            .with(MyCustomDsl.customDsl()) {
                disable()
            }
            // ...
        return http.build()
    }

}








Post Processing Configured Objects


Spring Security’s Java configuration does not expose every property of every object that it configures.
This simplifies the configuration for a majority of users.
After all, if every property were exposed, users could use standard bean configuration.spring-doc.cadn.net.cn


While there are good reasons to not directly expose every property, users may still need more advanced configuration options.
To address this issue, Spring Security introduces the concept of an ObjectPostProcessor, which can be used to modify or replace many of the Object instances created by the Java Configuration.
For example, to configure the filterSecurityPublishAuthorizationSuccess property on FilterSecurityInterceptor, you can use the following:spring-doc.cadn.net.cn



@Bean
public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
	http
		.authorizeHttpRequests(authorize -> authorize
			.anyRequest().authenticated()
			.withObjectPostProcessor(new ObjectPostProcessor<FilterSecurityInterceptor>() {
				public <O extends FilterSecurityInterceptor> O postProcess(
						O fsi) {
					fsi.setPublishAuthorizationSuccess(true);
					return fsi;
				}
			})
		);
	return http.build();
}

1	Configure Authentication as usual.
2	Create an instance of `SecurityFilterChain` that contains `@Order` to specify which `SecurityFilterChain` should be considered first.
3	The `http.securityMatcher` states that this `HttpSecurity` is applicable only to URLs that start with `/api/`.
4	Create another instance of `SecurityFilterChain`. If the URL does not start with `/api/`, this configuration is used. This configuration is considered after `apiFilterChain`, since it has an `@Order` value after `1` (no `@Order` defaults to last).