If you are referring to a bean in your expression like so: `@webSecurity.check(authentication, request)`, it's recommended that you instead call the bean directly, which will look something like the following:
For complex instructions that include bean references as well as other expressions, it is recommended that you change those to implement `AuthorizationManager` and refer to them by calling `.access(AuthorizationManager)`.
If you are not able to do that, you can configure a javadoc:org.springframework.security.web.access.expression.DefaultHttpSecurityExpressionHandler[] with a bean resolver and supply that to `WebExpressionAuthorizationManager#setExpressionhandler`.
If you are not able to do that, you can publish javadoc:org.springframework.security.web.access.expression.WebExpressionAuthorizationManager$Builder[] as a bean:
@ -51,11 +54,20 @@ public final class WebExpressionAuthorizationManager implements AuthorizationMan
@@ -51,11 +54,20 @@ public final class WebExpressionAuthorizationManager implements AuthorizationMan
Assert.notNull(expressionHandler,"expressionHandler cannot be null");
this.expressionHandler=expressionHandler;
@ -82,4 +94,78 @@ public final class WebExpressionAuthorizationManager implements AuthorizationMan
@@ -82,4 +94,78 @@ public final class WebExpressionAuthorizationManager implements AuthorizationMan