Browse Source

Replacing use of deprecated 'check' in authorization documentation

check() was deprecated in Spring Security 7, but was referenced in documentation

Signed-off-by: Fr05ty-hub <frostylucas@gmail.com>
pull/18500/head
Fr05ty-hub 3 weeks ago committed by Rob Winch
parent
commit
ed774d3595
  1. 2
      docs/modules/ROOT/pages/servlet/authorization/architecture.adoc

2
docs/modules/ROOT/pages/servlet/authorization/architecture.adoc

@ -107,7 +107,7 @@ default void verify(Supplier<Authentication> authentication, Object secureObject @@ -107,7 +107,7 @@ default void verify(Supplier<Authentication> authentication, Object secureObject
}
----
The ``AuthorizationManager``'s `check` method is passed all the relevant information it needs in order to make an authorization decision.
The ``AuthorizationManager``'s `authorize` method is passed all the relevant information it needs in order to make an authorization decision.
In particular, passing the secure `Object` enables those arguments contained in the actual secure object invocation to be inspected.
For example, let's assume the secure object was a `MethodInvocation`.
It would be easy to query the `MethodInvocation` for any `Customer` argument, and then implement some sort of security logic in the `AuthorizationManager` to ensure the principal is permitted to operate on that customer.

Loading…
Cancel
Save