[SHIRO-287] Enable web-configured SecurityManager to be statically accessible for non-request threads

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Labels: SecurityManager Shiro request static thread web web.xml
• Assignee: Les Hazlewood
• Reporter: Les Hazlewood
• Created: 21/Apr/11 02:20
• Updated: 24/Jan/12 01:11
• Resolved: 07/Jan/12 03:44

Description

For any work done on threads that are not triggered by a request thread, the SecurityManager should be accessible to these threads so the Subject.Builder can be used properly.

This can be accomplished by setting the configured SecurityManager as a static member variable in SecurityUtils (via SecurityUtils.setSubjectManager). While static memory is not ideal, it is probably good enough for 90% of web applications, and can be a viable solution.

Issue Links

• relates to: SHIRO-291 Provide ServletContextListener for initializing Shiro SecurityManager