首页 文章

使用EvaluationContextExtensionSupport和自定义PermissionEvaluator将Spring Boot 2.0.6迁移到2.1.0时'Invalid bean definition'

提问于
浏览
6

在Spring Boot 2.1.0中, EvaluationContextExtensionSupport 已弃用,https://docs.spring.io/spring-data/commons/docs/current/api/org/springframework/data/repository/query/spi/EvaluationContextExtensionSupport.html表示直接实施EvaluationContextExtension

即使它只是被弃用,它立即开始使用此堆栈跟踪进行此升级失败:

Caused by: org.springframework.beans.factory.support.BeanDefinitionOverrideException: Invalid bean definition with name 'methodSecurityInterceptor' defined in class path resource [org/springframework/security/config/annotation/method/configuration/GlobalMethodSecurityConfiguration.class]: Cannot register bean definition [Root bean: class [null]; scope=; abstract=false; lazyInit=false; autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration; factoryMethodName=methodSecurityInterceptor; initMethodName=null; destroyMethodName=(inferred); defined in class path resource [org/springframework/security/config/annotation/method/configuration/GlobalMethodSecurityConfiguration.class]] for bean 'methodSecurityInterceptor': There is already [Root bean: class [null]; scope=; abstract=false; lazyInit=false; autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=methodSecurityConfiguration; factoryMethodName=methodSecurityInterceptor; initMethodName=null; destroyMethodName=(inferred); defined in class path resource [ournamespace/configuration/MethodSecurityConfiguration.class]] bound.
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.registerBeanDefinition(DefaultListableBeanFactory.java:894)
    at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForBeanMethod(ConfigurationClassBeanDefinitionReader.java:274)
    at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:141)
...and so on

我不认为这只是我们当前代码中所做的一个副作用 . 如果我根据https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.1-Release-Notes#bean-overriding允许bean覆盖 spring.main.allow-bean-definition-overriding=true ,那么我只是得到另一个异常 .

java.lang.IllegalStateException: Duplicate key org.springframework.data.spel.ExtensionAwareEvaluationContextProvider$EvaluationContextExtensionAdapter@10dfbbbb at java.util.stream.Collectors.lambda$throwingMerger$0(Collectors.java:133) ~[na:1.8.0_162]

但是,我甚至不想覆盖任何bean行为,目标是让Spring自定义权限评估器再次按照Spring的意图工作 .

This is how it did work in the last version:

在Spring Boot 2.0.6中,我们有以下内容来使我们的自定义PermissionEvaluator类工作:

一个扩展 EvaluationContextExtensionSupport 的类

import org.springframework.data.repository.query.spi.EvaluationContextExtensionSupport;
import org.springframework.security.access.expression.SecurityExpressionRoot;
import org.springframework.security.core.Authentication;
import org.springframework.security.core.context.SecurityContextHolder;

public class SecurityEvaluationContextExtension extends EvaluationContextExtensionSupport {

    @Override
    public String getExtensionId() {
        return "security";
    }

    @Override
    public SecurityExpressionRoot getRootObject() {
        Authentication authentication = SecurityContextHolder.getContext().getAuthentication();
            return new SecurityExpressionRoot(authentication) {
        };
    }
}

然后是一个使用我们的权限评估程序创建表达式处理程序的类,并使用带有 EvaluationContextExtension 的@Bean

import ournamespace.security.CustomPermissionEvaluator;
import ournamespace.security.SecurityEvaluationContextExtension;
import lombok.RequiredArgsConstructor;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.data.repository.query.spi.EvaluationContextExtension;
import org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler;
import org.springframework.security.access.expression.method.MethodSecurityExpressionHandler;
import org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration;

@Configuration
@RequiredArgsConstructor
public class MethodSecurityConfiguration extends GlobalMethodSecurityConfiguration {

    private final CustomPermissionEvaluator permissionEvaluator;

    @Override
    protected MethodSecurityExpressionHandler createExpressionHandler() {
        DefaultMethodSecurityExpressionHandler expressionHandler =
                new DefaultMethodSecurityExpressionHandler();
        expressionHandler.setPermissionEvaluator(permissionEvaluator);
        return expressionHandler;
    }

    @Bean
    EvaluationContextExtension securityExtension() {
        return new SecurityEvaluationContextExtension();
    }
}

最后我们在一个基本上是空的类中有这个:

@EnableGlobalMethodSecurity(prePostEnabled = true)
public class WebSecurityConfiguration extends WebSecurityConfigurerAdapter {
   ...
}

这是因为如果我们将它放在 MethodSecurityConfiguration 类中,自定义权限评估程序从未应用于所有方法 . 有问题的服务器是oauth2资源服务器,因此我们不在 WebSecurityConfigurerAdapter 中配置任何其他服务器 . 我们还实现了自己的 UserDetails ,如果这与新解决方案有任何相关性,我们会扩展 DefaultUserAuthenticationConverter .

我已尝试直接实现 EvaluationContextExtension 类,如弃用警告中所述 . 通过将extends接口更改为 implements EvaluationContextExtension ,这只是一个简单的修改 . 我也尝试过换成看似更新的包 org.springframework.data.spel.spi

我已经尝试删除我们自己的 SecurityEvaluationContextExtension 并直接返回https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/data/repository/query/SecurityEvaluationContextExtension.html作为bean但由于某种原因,数据包在Spring Boot 2.1.0中不可用

我试过完全删除那个bean的定义 .

所有这些都会导致启动时出现各种“无效的bean定义”错误 .

有谁知道在哪里可以找到迁移指南或任何其他资源,了解它现在应该如何工作?

仅供参考,实际 CustomPermissionEvaluator 类:

import ournamespace.configuration.Constants;
import ournamespace.exception.InternalException;
import ournamespace.model.Account;
import ournamespace.model.Member;
import ournamespace.model.Project;
import ournamespace.repository.MemberRepository;
import ournamespace.service.ServiceUtil;
import lombok.RequiredArgsConstructor;
import org.springframework.security.access.PermissionEvaluator;
import org.springframework.security.core.Authentication;
import org.springframework.stereotype.Component;

import java.io.Serializable;

import static ournamespace.model.MemberStatus.JOINED;
import static ournamespace.model.ProjectRole.*;

@RequiredArgsConstructor
@Component
public class CustomPermissionEvaluator implements PermissionEvaluator {

    private final MemberRepository memberRepository;

    @Override
    public boolean hasPermission(Authentication auth, Object targetDomainObject, Object permission) {
        if (targetDomainObject == null)
            return false;

        if (!(permission instanceof String))
            return false;

        if (auth == null)
            return false;

        Account account = ServiceUtil.getAccount(auth);

        if (targetDomainObject instanceof Project)
            return hasPermissionOnProject(account, (Project) targetDomainObject, (String) permission);
        //and so on
    }
}

以及如何使用它的示例:

public interface ProjectRepository extends PagingAndSortingRepository<Project, UUID> {

    @Override
    @PreAuthorize("hasPermission(#project, " + Constants.WRITE + ")")
    <S extends Project> S save(@Param("project") S project);
}

2 回答

  • 3

    我拿了你的代码并从中创建了一个示例应用程序 . 我在这里发布了:

    https://github.com/jzheaux/stackoverflow-53410526

    您的 @EnableGlobalMethodSecurity 注释位于 WebSecurityConfigurerAdapter . 您还有一个扩展 GlobalMethodSecurityConfiguration 的类 . 这可能会在启动时导致一些排序问题,这可能是您所看到的=>两个 MethodSecurityExpressionHandler s被创建以及两个 EvaluationContextExtension s .

    无论这是否正是如此(我猜它确实如此),当我将 @EnableGlobalMethodSecurity 与您的自定义 GlobalMethodSecurityConfiguration 匹配时,事情就开始了 .

    但是,您的自定义 EvaluationContextExtension 似乎与Spring Security默认值非常相似 . 如果可以的话,您可以考虑删除该类以及相应的bean方法,因为当您将 spring-boot-starter-securityspring-security-data 作为依赖项时,Spring Boot会自动公开一个 .

  • 2

    你正在重写 methodSecurityInterceptor bean . 之前它正在工作,因为允许bean覆盖 .

    默认情况下已禁用Bean重写以防止意外覆盖Bean . 如果依赖于覆盖,则需要将spring.main.allow-bean-definition-overriding设置为true .

    Spring-Boot-2.1-Release-Notes#bean-overriding

相关问题