spring-boot

Commit Graph

Author	SHA1	Message	Date
Rob Baily	3c50386970	Fix logout in sample secure web applications Fixes gh-1536	10 years ago
Phillip Webb	61fc4f3f12	Polish copyright headers	10 years ago
Phillip Webb	1ce617f1ae	Polish sample package names	10 years ago
Phillip Webb	a57a88f5cf	Move master to 1.3.0.BUILD-SNAPSHOT	10 years ago
Spring Buildmaster	8f0ad02237	Next development version	10 years ago
Spring Buildmaster	60725cd8bd	Next development version	10 years ago
Phillip Webb	5afd0b4858	Polish sample POM names	10 years ago
Spring Buildmaster	1a788c1741	Next development version	10 years ago
Dave Syer	5fd9af23d6	Merge branch '1.1.x'	10 years ago
Dave Syer	607f78a779	Add secure sample with JDBC and data.sql We can't easily solve the problem by not allowing Spring Security to eagerly instantiate everything, but we can be defensive about data.sql and make sure it is executed even if the listener isn't yet registered. Fixes gh-1386	10 years ago
Phillip Webb	6634af6a25	Fix broken parent POM version Update the parent POM version in spring-boot-sample-web-secure-custom	10 years ago
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	10 years ago

12 Commits (e9a6245a44c194f239fa0cf33f7cbd398a52e1ac)