Spring Security SEC-3004: Allow access to WebInvocationPrivilegeEvaluator when using multiple <http>

Mattias Jiderhamn (Migrated from SEC-3004) said:

When using a Spring Security configuration with a single <http> entry, you can easily get hold of the the WebInvocationPrivilegeEvaluator by auto wiring.

However that is not so easy when using multiple <http>, because it is neither possible to supply a WebInvocationPrivilegeEvaluator nor to provide a name for the autowiring capable DefaultWebInvocationPrivilegeEvaluator s being created by HttpConfigurationBuilder.createFilterSecurityInterceptor(), leading to the infamous expected single matching bean but found N.

Comment From: marcusdacoregio

Fixed via https://github.com/spring-projects/spring-security/pull/10575