shiro报错No SecurityManager accessible to the calling code, either bound to the org.apache.shiro

已于 2023-08-11 13:44:39 修改
阅读量5.6k 收藏 8
点赞数 11
分类专栏： java shiro 文章标签： java shiro
于 2023-06-12 21:46:59 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/japhet_jiu/article/details/131177210
版权
java 同时被 2 个专栏收录
23 篇文章 3 订阅
订阅专栏
shiro
1 篇文章 0 订阅
订阅专栏

问题

今天在调试代码的时候，报了这么一个错，排查半天，终于找到解决方法，具体报错如下图

No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton.This is an invalid application configuration

16:29:03.059 [http-nio-80-exec-25] ERROR o.a.c.c.C.[.[.[.[dispatcherServlet] - [log,175] - Servlet.service() for servlet [dispatcherServlet] threw exception
org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton.  This is an invalid application configuration.
	at org.apache.shiro.SecurityUtils.getSecurityManager(SecurityUtils.java:123)
	at org.apache.shiro.subject.Subject$Builder.<init>(Subject.java:626)
	at org.apache.shiro.SecurityUtils.getSubject(SecurityUtils.java:56)
	at org.apache.shiro.web.servlet.ShiroHttpServletRequest.getSubject(ShiroHttpServletRequest.java:89)
	at org.apache.shiro.web.servlet.ShiroHttpServletRequest.getSession(ShiroHttpServletRequest.java:154)
	at org.springframework.web.util.WebUtils.getSessionId(WebUtils.java:359)
	at org.springframework.web.servlet.FrameworkServlet.publishRequestHandledEvent(FrameworkServlet.java:1145)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1023)
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:655)
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:102)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:102)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:711)
	at org.apache.catalina.core.ApplicationDispatcher.doDispatch(ApplicationDispatcher.java:632)
	at org.apache.catalina.core.ApplicationDispatcher.dispatch(ApplicationDispatcher.java:600)
	at org.apache.catalina.core.AsyncContextImpl$AsyncRunnable.run(AsyncContextImpl.java:587)
	at org.apache.catalina.core.AsyncContextImpl.doInternalDispatch(AsyncContextImpl.java:353)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:194)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
	at org.apache.catalina.connector.CoyoteAdapter.asyncDispatch(CoyoteAdapter.java:250)
	at org.apache.coyote.AbstractProcessor.dispatch(AbstractProcessor.java:241)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:59)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:748)
16:29:03.060 [http-nio-80-exec-25] ERROR o.a.c.c.C.[.[.[.[dispatcherServlet] - [log,175] - Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [java.lang.RuntimeException: Error during asynchronous dispatch] with root cause
org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton.  This is an invalid application configuration.
	at org.apache.shiro.SecurityUtils.getSecurityManager(SecurityUtils.java:123)
	at org.apache.shiro.subject.Subject$Builder.<init>(Subject.java:626)
	at org.apache.shiro.SecurityUtils.getSubject(SecurityUtils.java:56)
	at org.apache.shiro.web.servlet.ShiroHttpServletRequest.getSubject(ShiroHttpServletRequest.java:89)
	at org.apache.shiro.web.servlet.ShiroHttpServletRequest.getSession(ShiroHttpServletRequest.java:154)
	at org.springframework.web.util.WebUtils.getSessionId(WebUtils.java:359)
	at org.springframework.web.servlet.FrameworkServlet.publishRequestHandledEvent(FrameworkServlet.java:1145)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1023)
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:655)
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:102)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:102)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:711)
	at org.apache.catalina.core.ApplicationDispatcher.doDispatch(ApplicationDispatcher.java:632)
	at org.apache.catalina.core.ApplicationDispatcher.dispatch(ApplicationDispatcher.java:600)
	at org.apache.catalina.core.AsyncContextImpl$AsyncRunnable.run(AsyncContextImpl.java:587)
	at org.apache.catalina.core.AsyncContextImpl.doInternalDispatch(AsyncContextImpl.java:353)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:194)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
	at org.apache.catalina.connector.CoyoteAdapter.asyncDispatch(CoyoteAdapter.java:250)
	at org.apache.coyote.AbstractProcessor.dispatch(AbstractProcessor.java:241)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:59)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:748)

问题解析

是因为Apache Shiro无法找到SecurityManager。在Apache Shiro中，SecurityManager是中心安全控制器，所有安全相关的操作都会与它交互。这个错误可能的原因是没有正确地设置或者初始化Shiro的SecurityManager。

解决方案

在调用接口处添加以下代码（初始化一下）

        DefaultSecurityManager securityManager = new DefaultSecurityManager();
        SecurityUtils.setSecurityManager(securityManager);

问题要是解决了，记得点个赞

 如果小伙伴们有什么疑问，欢迎下面评论。欢迎指正。如还有什么不懂的加我 QQ：517861659

如果没有及时回复，可以点我先问问AI机器人https://chatgpt.byabstudio.com/login?code=202307011314

Japhet_jiu
关注
专栏目录
Spirng Boot +Shiro 系统执行初始化数据时报No SecurityManager accessible to the calling code异常
xuyp95的博客
06-15 3618
Spirng Boot +Shiro 系统执行初始化数据时报No SecurityManager accessible to the calling code异常环境出现背景异常信息解决方法完整的shiroConfiguration类 环境 Spring Boot + Shiro 出现背景 使用Spring Boot 的ApplicationRunner接口去执行数据库初始化数据。在执行过程中的保...
Shiro报错 No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util
hestyle的博客
01-20 1万+
Shiro报错 1、报错详情 org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static single...
Shiro报错No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.
热门推荐
小单的博客专栏
03-18 5万+
问题描述： 项目使用 SpringMVC 并使用 Shiro 来管理Session控制权限。经常会不定期的发现异常：org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.
Shiro报错：No SecurityManager accessible to the calling code, either bound to the...的几种情况
uu的博客
08-14 495
的时候，没有找到SecurityManager。这种报错可能是正常的 也可以能是异常的。本文将就这两种情况进行说明。
No SecurityManager accessible to the calling code 错误解决方式
weixin_44692699的博客
10-19 2万+
Cause: org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton. This is an invalid application configuration. 上方报错的几种可能 唯
vue前后端交互学习问题记录2
2201_75308743的博客
08-09 1158
deep为深度监听，对象和数组都是复杂数据类型，复杂数据类型存的是地址值，地址没有变，不会触发watch。这时我们需要进行深度监听，就需要加上一个属性 deep，值设为 true，使用deep属性可以监测到整个对象所有属性值的变化，某个属性发生变化，watch都会触发监听该对象。其中"dataForm.creatTime"所在的位置是要监听的变量，newVal为该变量的新值，一旦newVal为null就将要监听的变量置为你想要的值。重新启动项目，定时任务正常运行。重新刷新配置后就能正常使用了。
Shiro报错No SecurityManager accessible to the calling code
blog：xuchuruo.cn
10-16 3万+
HTTP Status 500 - No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton. This is an invalid application configuration. ...
【问题集锦】No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.T
若释·飞语
03-02 2312
这个方法正好是在报错中调用失败的方法，所以我们只需要给他初始化一个。具体实现代码如下，在注册bean的时候，加入下面这句话，将。今天，趁着周末，我决定解决这个问题。最近自己在弄一套后台程序，在集成。，而在shiro中提供了一种设置。的操作使用了单例模式，通过。
Shiro错误之No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util
Mint6的博客
02-16 2万+
提示： No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton. 具体错误信息如下： 18:35:03.909 ERROR org.apache.juli.logging.Di...
报错No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.Threa
x_c_yang的博客
02-20 4860
本人在开发现在的web项目中的时候，碰到了一个问题，大概就是说调用不到SecurityManager。报错的是其中一个Controller，上网查了一下，看了下代码，定位到了类的开头定义的一个通过Shiro获取用户的登录名的变量。一开始以为我是因为final关键字不能修饰session这种动态的变量。后面删除final也没有变化还是报错。之后我把从Shiro获取用户名删掉，只用字符串的时候就可以运...
shiro报错:No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util
思苑
03-03 2549
一、问题描述 二、解决办法 我的原因并不是shirofilter谁先谁后的问题也不是shirofilter写在哪里的问题，通过观察日志找到对应的错误类的方法 改成如下，问题解决。 public static Long getUserId() { // if (null != getAuthUser()) { // return getAuthUser().getUserId(); /...
Spring Boot整合Shiro 获取subject对象报错No SecurityManager accessible to the calling code的问题
al_student的博客
10-18 1445
Spring Boot整合Shiro 获取subject对象报错，No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton. This is an invalid application configuration.
SpringMVC配置错误页后, Shiro报错No SecurityManager accessible to the calling code...
Excaliburace的博客
09-27 6852
Root Cause:org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton.
No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton.
最新发布
09-24
如果代码没有绑定到`org.apache.shiro.util.ThreadContext`（一个用于存储当前会话上下文的工具类），也没有将其设置为虚拟机的静态单例，那么就无法获取到有效的安全管理器。 原因可能是： 1. 没有在应用程序初始...
springboot整合shiro启动报 No SecurityManager accessible to the calling code...错误
m0_53428367的博客
12-13 1388
springboot整合shiro启动报 No SecurityManager accessible to the calling code...错误
Shiro报错UnavailableSecurityManagerException
z2014ypd的博客
04-01 3709
运行整合了shiro的spring报错： org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code,either bound to the org.apache.shiro.util.ThreadContext or as a vm static s...
No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util....
qq_38190111的博客
01-03 1578
spring boot 搭建 shiro 框架报错 配置报错，然后以下有关shiro的配置都写好的情况下： public class ShiroConfiguration { /** * Shiro的Web过滤器Factory 命名:shiroFilter */ @Bean(name = "shiroFilter") public ShiroFi...
No SecurityManager accessible to the calling code
t518vs20s的博客
11-24 3489
org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton. This is a...
No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton
11-09
个错误信息意味着调用代码无法访问任何SecurityManager实例，这可能是因为没有将SecurityManager绑定到ThreadContext或作为vm静态单例绑定。这是一个无效的应用程序配置。在Shiro框架中，SecurityManager是核心组件之一，它通过管理内部组件实例来提供各种安全管理服务。Realm则充当了Shiro与应用程序安全数据之间的“桥梁”或“连接器”，它负责从数据源中获取安全数据并将其提供给Shiro进行身份验证和授权。因此，要解决这个错误，需要确保正确配置了SecurityManager并将其绑定到ThreadContext或作为vm静态单例绑定。
评论 5
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值