GitHub-Spring/spring-boot - spring-boot - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Dave Syer	0cf1c6f0e5	Refactor AuthenticationManagerConfiguration to make sure it works if user also adds @EnableWebMvcSecurity. The problem is that the ordering of the init() and configure() methods in the Spring Security configurers can force things to happen too early unless we are careful. It's still a bit twitchy I would say, but this relatively small change seems to fix the GS guide and not break any existing tests. I added a sample which mimic ths GS guide so we get an integration test that executes the new code paths. Fixes gh-1364	12 years ago
Phillip Webb	fa88c481a5	Remote trailing whitespace	12 years ago
Phillip Webb	468728a2c0	Polish	12 years ago
Dave Syer	b0b7bc0e7f	Fix tests Some assumptions were being made in tests, e.g. about there being an AuthenticationManager @Bean, which were false with the new Security 3.2.1 updates from Rob. Also parent-child contexts with the actuator were problematic because they didn't exclude the web configuration for the management security in the parent context. Fixes gh-244	12 years ago
Phillip Webb	ed9735361e	Apply source cleanup and formatting	12 years ago
Dave Syer	4d608f20e9	Support for AuthenticationManagerBuilder injection into user code Spring Boot provides a default AuthenticatiomManager for getting started quickly with security and never exposing insecure endpoints. To override that feature as users move to the next stage in their project, they may have to do something slightly different depending on whether it is a webapp or not. In any app (web or not), providing a @Bean of type AuthenticationManager always works, but you don't get the benefit of the builder features. In a webapp the user can also extend WebSecurityConfigurerAdapter to provides a custom AuthenticationManager, and the preferred way of doing that is via a void method that is autowired with an AuthenticationManagerBuilder. The default AuthenticationManager is built in a configurer with @Order(LOWEST_PRECEDENCE - 3) so to override it the user's confugrer must have higher precedence (lower @Order). @EnableGlobalMethodSecurity can also be used in a non-webapp, and Spring Boot will still provide a default AuthenticationManager. To override it the user has to either extend GlobalMethodSecurityConfiguration or provide a @Bean of type AuthenticationManager (there's no other way to capture the AuthenticationManagerBuilder that doesn't happen too late in the beans lifecyle). Fixes gh-244	12 years ago
Phillip Webb	0160760568	Apply latest eclipse cleanup rules	12 years ago
Phillip Webb	cdda330acd	Update copyright header for files changed in 2014	12 years ago
Dave Syer	b1db714c23	Allow @EnableGlobalMethodSecurity in a non webapp Fixes gh-202	12 years ago