[
https://issues.apache.org/jira/browse/SHIRO-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lenny Primak closed SHIRO-648.
------------------------------
Resolution: Not A Problem
Use latest Shiro to resolve the issue, if unresolved, please open GitHub issue
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
