Add Caveat about Spring Security's co-routine support
Closes gh-10920
This commit is contained in:
parent
cbb4f40f0c
commit
27ce5936cf
|
@ -6,10 +6,17 @@ For example, this demonstrates how to retrieve the currently logged in user's me
|
|||
|
||||
[NOTE]
|
||||
====
|
||||
For this to work the return type of the method must be a `org.reactivestreams.Publisher` (i.e. `Mono`/`Flux`) or the function must be a Kotlin coroutine function.
|
||||
For this to work the return type of the method must be a `org.reactivestreams.Publisher` (for example, `Mono`/`Flux`).
|
||||
This is necessary to integrate with Reactor's `Context`.
|
||||
====
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
Method Security also supports Kotlin coroutines, though only to a limited degree.
|
||||
When intercepting coroutines, only the first interceptor participates.
|
||||
If any other interceptors are present and come after Spring Security's method security interceptor, they will be skipped.
|
||||
====
|
||||
|
||||
====
|
||||
.Java
|
||||
[source,java,role="primary"]
|
||||
|
|
Loading…
Reference in New Issue