Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEC-3004: Allow access to WebInvocationPrivilegeEvaluator when using multiple <http> #3142

Closed
spring-projects-issues opened this issue Jun 10, 2015 · 1 comment
Assignees
Labels
in: web An issue in web modules (web, webmvc) status: duplicate A duplicate of another issue type: bug A general bug type: jira An issue that was migrated from JIRA

Comments

@spring-projects-issues
Copy link

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.

@marcusdacoregio
Copy link
Contributor

Fixed via #10575

@marcusdacoregio marcusdacoregio added in: web An issue in web modules (web, webmvc) and removed in: core An issue in spring-security-core labels Dec 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web An issue in web modules (web, webmvc) status: duplicate A duplicate of another issue type: bug A general bug type: jira An issue that was migrated from JIRA
Projects
None yet
Development

No branches or pull requests

3 participants