anchor.diff:  More technically speaking, Spring Security integrates with `WebAsyncManager`. The `SecurityContext` that is used to process the `Callable` is the `SecurityContext` that exists on the `SecurityContextHolder` at the time `startCallableProcessing` is invoked.
   ====
   
  -There is no automatic integration with a `DeferredResult` that is returned by controllers. This is because `DeferredResult` is processed by the users and thus there is no way of automatically integrating with it. However, you can still use <<concurrency-support>> to provide transparent integration with Spring Security.
  +There is no automatic integration with a `DeferredResult` that is returned by controllers.
  +This is because `DeferredResult` is processed by the users and thus there is no way of automatically integrating with it.
  +However, you can still use <<concurrency,Concurrency Support>> to provide transparent integration with Spring Security.
   
   [[mvc-csrf]]
   === Spring MVC and CSRF Integration
  
positive.code: 
  [[ldap-searchobjects-filter]]
  ===== FilterBasedLdapUserSearch
  This bean uses an LDAP filter to match the user object in the directory. The process is explained in the Javadoc for the corresponding search method on thehttp://java.sun.com/j2se/1.4.2/docs/api/javax/naming/directory/DirContext.html#search(javax.naming.Name,%20java.lang.String,%20java.lang.Object[],%20javax.naming.directory.SearchControls)[JDK DirContext class]. As explained there, the search filter can be supplied with parameters. For this class, the only valid parameter is `{0}` which will be replaced with the user's login name.
  
  
  [[ldap-authorities]]
  
negative.code: [[nsa-websocket-message-broker]]
  ==== <websocket-message-broker>
  
  The websocket-message-broker element has two different modes.
  If the <<nsa-websocket-message-broker-id,websocket-message-broker@id>> is not specified, then it will do the following things:
  
  * Ensure that any SimpAnnotationMethodMessageHandler has the AuthenticationPrincipalArgumentResolver registered as a custom argument resolver. This allows the use of `@AuthenticationPrincipal` to resolve the principal of the current `Authentication`
  * Ensures that the SecurityContextChannelInterceptor is automatically registered for the clientInboundChannel. This populates the SecurityContextHolder with the user that is found in the Message
  