@ -203,6 +203,11 @@ public class MethodSecurityServiceImpl implements MethodSecurityService {
@@ -203,6 +203,11 @@ public class MethodSecurityServiceImpl implements MethodSecurityService {
@ -1410,6 +1411,14 @@ public class PrePostMethodSecurityConfigurationTests {
@@ -1410,6 +1411,14 @@ public class PrePostMethodSecurityConfigurationTests {
@ -285,6 +287,15 @@ public class ReactiveMethodSecurityConfigurationTests {
@@ -285,6 +287,15 @@ public class ReactiveMethodSecurityConfigurationTests {
@ -100,6 +100,11 @@ public class ReactiveMethodSecurityServiceImpl implements ReactiveMethodSecurity
@@ -100,6 +100,11 @@ public class ReactiveMethodSecurityServiceImpl implements ReactiveMethodSecurity
@ -91,7 +91,7 @@ public final class PostAuthorizeReactiveAuthorizationManager
@@ -91,7 +91,7 @@ public final class PostAuthorizeReactiveAuthorizationManager
@ -85,7 +85,7 @@ public final class PreAuthorizeReactiveAuthorizationManager
@@ -85,7 +85,7 @@ public final class PreAuthorizeReactiveAuthorizationManager
@ -1362,6 +1362,12 @@ Note, though, that returning an object is preferred as this doesn't incur the ex
@@ -1362,6 +1362,12 @@ Note, though, that returning an object is preferred as this doesn't incur the ex
Then, you can access the custom details when you <<fallback-values-authorization-denied, customize how the authorization result is handled>>.
[TIP]
====
Further, you can return an `AuthorizationManager` itself.
This is helpful when unifying custom web authorization rules with method security ones since web security by default requires specifying an `AuthorizationManager` instance.