You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2018/02/15 22:04:00 UTC
[jira] [Commented] (KNOX-997) call to Shiro Subject logout method
get an exception. - Invalid configuration.
[ https://issues.apache.org/jira/browse/KNOX-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366322#comment-16366322 ]
Larry McCay commented on KNOX-997:
----------------------------------
[~jeffreyr97] - we are still waiting on this patch - or have you committed it as part of a duplicate JIRA?
> call to Shiro Subject logout method get an exception. - Invalid configuration.
> -------------------------------------------------------------------------------
>
> Key: KNOX-997
> URL: https://issues.apache.org/jira/browse/KNOX-997
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.13.0
> Environment: all
> Reporter: Jeffrey E Rodriguez
> Assignee: Jeffrey E Rodriguez
> Priority: Major
> Fix For: 1.1.0
>
>
> call to Shiro subject logout method causes exception.
> Applications that want to invalidate sessions in Knox by caling Shiro Subject logout method or other methods requiring a Shiro Security Manager may get an 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."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)