- 27 May, 2015 2 commits
-
-
Stephane Nicoll authored
Closes gh-2851
-
Stephane Nicoll authored
-
- 26 May, 2015 15 commits
-
-
Stephane Nicoll authored
Allow SSL to be configured via standard configuration as well as the requestedHeartbeat. Switch to RabbitConnectionFactoryBean. Closes gh-2655, gh-2676
-
Stephane Nicoll authored
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Do not rely on the packaging type to figure out what the extension of the main artifact will be. So far, using `jar` and `war` packaging for `.jar` and `.war` files worked by chance. We know retrieve the actual extension as provided by Maven's `ArtifactHandler`. Fixes gh-2762
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Fix `excludeAgentPatterns`, `excludePaths` and `excludePathPatterns` properties. Introduce `excludedMimeTypes` property. Fixes gh-3042
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Rework c03e14be to avoid an extra empty space in log message See gh-3033
-
Stephane Nicoll authored
-
Stephane Nicoll authored
* patch-10: Fix broken link in doc
-
izeye authored
Closes gh-3040
-
Dave Syer authored
User can enable OAuth2 SSO by declaring the intent (@EnableOAuth2Sso) and also configuring the client properties (spring.oauth2.client.*). The spring.oauth2.sso.* are only needed to change the path for the login (defaults to /login) - any other security configuration for the protected resources can be added in a WebSecurityConfigurerAdapter which carries the @EnableOAuth2Sso annotation.
-
Dave Syer authored
-
Dave Syer authored
-
Greg Turnquist authored
* Automatically spin up Authorization Server and Resource Server * Automatically configures method level security included OAuth2Expression handler * Wrote extensive unit tests verifying default behavior as well as the auto-configuration backing off when custom Authorization/Resource servers are included * Created org.springframework.boot.security.oauth2 subpackage to contain it * Can also disable either resource of authorization server completely with a single property for each * Print out the auto-generated secrets and other settings * Added spring-boot-sample-secure-oauth2 to provide a sample that can be run and poked with curl as well as some automated tests. * Make users ask for which servers to install by adding @Enable* * User has to @EnableGlobalMethodSecurity instead of using properties files Add Spring Security OAuth2 support to Spring Boot CLI * Triggered from either @EnableAuthorizationServer or @EnableResourceServer * Needs to have @EnableGlobalMethodSecurity to allow picking the annotation model. * By default, comes with import support for @PreAuthorize, @PreFilter, @PostAuthorize, and @PostFilter via a single start import * Also need import support for the enable annotations mentioned above. * Added extra test case and sample (oauth2.groovy)
-
- 25 May, 2015 2 commits
-
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Fixes gh-3033
-
- 22 May, 2015 1 commit
-
-
Stephane Nicoll authored
Switch the condition used to trigger the creation of a transaction manager from the default name to the actual type. Fixes gh-3012
-
- 21 May, 2015 1 commit
-
-
Stephane Nicoll authored
Add an extra property to control the support of fallback resolution for mobile views. Fixes gh-3009, gh-3019
-
- 20 May, 2015 11 commits
-
-
Andy Wilkinson authored
Previously, to use a custom SpringApplicationBuilder subclass in SpringBootServletInitializer, it was necessary to either override createRootApplicationContext or configure and duplicate the logic that configures the builder with initializers, the context class, etc. This commit introduces a new method, createSpringApplicationBuilder, that can be overridden to use a custom builder without having to duplicate any configuration logic. Closes gh-2694
-
Andy Wilkinson authored
Closes gh-2099
-
Andy Wilkinson authored
-
Andy Wilkinson authored
- Apply project’s code formatting and conventions - Don’t use the IO and worker thread configuration when creating the worker for the AccessLogReceiver. The IO and worker thread configuration is for HTTP request processing and a worker in its default configuration should be sufficient for the access log receiver. - Don’t use a temporary directory as the default for the access log directory. A temporary directory makes (some) sense for Tomcat as it requires a directory for its basedir. Undertow has no such requirement and using a temporary directory makes it hard to locate the logs. The default has been updated to a directory named logs, created in the current working directory. - Document the new properties in the application properties appendix Closes gh-3014
-
Marcos Barbero authored
This commit adds support for configuring Undertow's access log via the environment using the following properties: server.undertow.access-log-enabled server.undertow.access-log-pattern server.undertow.access-log-dir See gh-3014
-
Andy Wilkinson authored
The internals have been updated so that the field that was originally used, interceptors, can be used again. This reverts commit 2a1bca68.
-
Stephane Nicoll authored
-
Joe Kutner authored
Closes gh-3000
-
Andy Wilkinson authored
-
Andy Wilkinson authored
Closes gh-2950
-
Andy Wilkinson authored
Closes gh-3015
-
- 19 May, 2015 8 commits
-
-
Andy Wilkinson authored
See gh-2699
-
Andy Wilkinson authored
Closes gh-2699
-
Andy Wilkinson authored
Previously, JacksonAutoConfiguration would register any Jackson Module beans with every ObjectMapper found in the application context. This was not consistent with the rest of the Jackson auto-configuration, which is only applied to ObjectMappers that are created or configured via the auto-configured Jackson2ObjectMapperBuilder. This commit removes the code that registers Jackson Module beans with every ObjectMapper. Such beans will still be registered with ObjectMappers created or configured using the auto-configured Jackson2ObjectMapperBuilder. This aligns the configuration of Module with the rest of the ObjectMapper configuration and makes it possible for users to create an ObjectMapper bean and still have complete control over the modules that are registered with it. Closes gh-2489
-
Andy Wilkinson authored
-
Andy Wilkinson authored
A recent change to the internals of RequestMappingHandlerMapping broke to Spring Mobile-related tests as they were using reflection to verify that the configuration had been applied correctly. This commit makes the tests more robust by using the Java API to access the interceptors for a request and verify that the expected interceptor is present. To further simplify the tests, the unnecessary use of an embedded servlet container factory has also been removed.
-
Andy Wilkinson authored
- Verify that isReady has been called - When forking, use a random port for JMX - Don’t wait for application termination as it introduces a race condition and verifying that shutdown has been requested is sufficient See gh-2525
-
Andy Wilkinson authored
Closes gh-3006
-
Andy Wilkinson authored
Closes gh-3005
-