Cwikius-Spring/spring-security
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-security.git synced 2025-07-30 06:03:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

SEC-2965: Fix invalid formatted links in reference documentation

Browse Source
This commit is contained in:
Rob Winch 2015-07-16 15:27:04 -05:00
parent 1ca5946d74
commit 518a1c3c08
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/manual/src/docs/asciidoc/index.adoc
View File

@ -6289,7 +6289,9 @@ return new Callable<String>() {
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
@ -6340,7 +6342,7 @@ Will output HTML that is similar to the following:
==== Resolving the CsrfToken
Spring Security provides `CsrfTokenResolver` which can automatically resolve the current `CsrfToken` for Spring MVC arguments.
By using <<mvc-enablewebsecurity>> you will automatically have this added to your Spring MVC configuration.
By using <<jc-hello-wsca,@EnableWebSecurity>> you will automatically have this added to your Spring MVC configuration.
If you use XML based configuraiton, you must add this yourself.
Once `CsrfTokenResolver` is properly configured, you can expose the `CsrfToken` to your static HTML based application.
@ -8013,7 +8015,8 @@ Spring Security 4.0+ provides support for authorizing messages. One concrete exa
[[nsa-websocket-message-broker]]
==== <websocket-message-broker>
The websocket-message-broker element has two different modes. If the <<nsa-websocket-id>> is not specified, then it will do the following things:
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