Replacing use of deprecated 'check' in authorization documentation

Fr05ty-hub · rwinch · commit ed774d35950a · 2026-01-09T15:27:00.000-06:00
check() was deprecated in Spring Security 7, but was referenced in documentation

Signed-off-by: Fr05ty-hub &lt;frostylucas@gmail.com&gt;
diff --git 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> 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.

Original file line number	Diff line number	Diff line change
`@@ -107,7 +107,7 @@ default void verify(Supplier<Authentication> authentication, Object secureObject`
`107`	`107`	`}`
`108`	`108`	`----`
`109`	`109`
`110`		-The ``AuthorizationManager``'s `check` method is passed all the relevant information it needs in order to make an authorization decision.
	`110`	+The ``AuthorizationManager``'s `authorize` method is passed all the relevant information it needs in order to make an authorization decision.
`111`	`111`	In particular, passing the secure `Object` enables those arguments contained in the actual secure object invocation to be inspected.
`112`	`112`	For example, let's assume the secure object was a `MethodInvocation`.
`113`	`113`	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.