From ed774d35950a6ecfe89239f8741b11d89c0940a2 Mon Sep 17 00:00:00 2001 From: Fr05ty-hub Date: Wed, 7 Jan 2026 12:03:13 +0100 Subject: [PATCH] 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 --- docs/modules/ROOT/pages/servlet/authorization/architecture.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/servlet/authorization/architecture.adoc b/docs/modules/ROOT/pages/servlet/authorization/architecture.adoc index 2955a7c028..545824f0ba 100644 --- a/docs/modules/ROOT/pages/servlet/authorization/architecture.adoc +++ b/docs/modules/ROOT/pages/servlet/authorization/architecture.adoc @@ -107,7 +107,7 @@ default void verify(Supplier 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.