[ https://issues.apache.org/jira/browse/KNOX-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366419#comment-16366419 ]
Jeffrey E Rodriguez commented on KNOX-997: ------------------------------------------- Hi Larry. Here is the patch. The fix was to setup Shiro security manager to the SecurityManager accessible to the calling code. [https://shiro.apache.org/static/1.3.2/apidocs/org/apache/shiro/SecurityUtils.html] It still needs a test to call Shiro Subject logout method. > 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 > > Attachments: KNOX-997.patch.001, KNOX-997.patch.001 > > > 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)