AOP通知导致controller接口访问失效，并且与shiro注解 @RequiresAuthentication冲突

最新推荐文章于 2025-07-29 18:39:42 发布

原创最新推荐文章于 2025-07-29 18:39:42 发布 · 696 阅读

2 ·

本内容遵循CC 4.0 BY-SA版权协议

标签

#springboot #maven

本文探讨了在Spring Boot应用中，如何避免LoginAspect与Shiro注解的冲突，并通过YAML配置AOP代理方式，同时介绍了处理接口访问失效的方法。重点在于处理AOP前置通知与Shiro认证的协调，适合前端后端分离项目的实践指南。

package com.separate.common.aspect;

import com.separate.util.JwtUtils;
import lombok.extern.slf4j.Slf4j;
import org.aspectj.lang.annotation.Aspect;
import org.aspectj.lang.annotation.Before;
import org.aspectj.lang.annotation.Pointcut;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.context.annotation.EnableAspectJAutoProxy;
import org.springframework.stereotype.Component;
import org.springframework.web.context.request.RequestContextHolder;
import org.springframework.web.context.request.ServletRequestAttributes;

import javax.annotation.Resource;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
//aop前置通知
@EnableAspectJAutoProxy(proxyTargetClass = true)
@Aspect
@Component
@Slf4j
public class LoginAspect {
	
    @Resource
    private JwtUtils jwtUtil;

    @Pointcut("execution(public * com.separate.controller.BusinessAllGoodsController.*(..))")
    public void verify() {}

    @Before("verify()")
    public void doVerify() {
        ServletRequestAttributes attributes = (ServletRequestAttributes) RequestContextHolder.getRequestAttributes();
        HttpServletRequest request = attributes.getRequest();
        HttpServletResponse response = attributes.getResponse();
        String token = jwtUtil.getJwtFromRequest(request);
        jwtUtil.parseJWT(token);
    }

}

1.接口访问失效，全部为404 解决方法：
在yml文件里设置aop的选择方案。

  aop:
    proxy-target-class: true//使用cglib false则使用jdk
    auto: true

2.与shiro注解@RequiresAuthentication冲突解决方案:
shiro.config里修改配置

@DependsOn("lifecycleBeanPostProcessor")
    @Bean
    public DefaultAdvisorAutoProxyCreator defaultAdvisorAutoProxyCreator() {
        DefaultAdvisorAutoProxyCreator proxyCreator = new DefaultAdvisorAutoProxyCreator();
        proxyCreator.setUsePrefix(true);
        return proxyCreator;
    }