[
https://issues.apache.org/jira/browse/SHIRO-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504741#comment-16504741
]
Brian Demers commented on SHIRO-648:
------------------------------------
This is likely an issue with how Geode is configured.
Typically you wouldn't call {{curentUser.login(token)}} directly. Instead the
underlying framework would do this.
Can you provide more information about the request? Is it made within the
context of a servlet request? Is it async?
Take a look at: https://shiro.apache.org/subject.html#thread-association
> SecurityUtils.getSubject() throws
> org.apache.geode.security.AuthenticationFailedException intermittently
> --------------------------------------------------------------------------------------------------------
>
> Key: SHIRO-648
> URL: https://issues.apache.org/jira/browse/SHIRO-648
> Project: Shiro
> Issue Type: Bug
> Components: Authentication (log-in)
> Affects Versions: 1.3.2
> Reporter: Jinmei Liao
> Priority: Major
>
> When our application starts, we set the vm static SecurityManager using
> {code:java}
> SecurityUtils.setSecurityManager(xyz);
> {code}
> But sometimes when we do login using:
> {code:java}
> Subject currentUser = SecurityUtils.getSubject();
> curentUser.login(tokent)
> {code}
> we occasionally get the following exception:
> {code:java}
> org.apache.geode.security.AuthenticationFailedException: 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.
> {code}
> We suspect that it's because the vm static SecurityManager is not volatile
> and not visible to the login thread....
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
