That apparently isn't being used anymore - I need to remove it. In short, the SecurityManager instance is bound to the currently executing thread for use in the SecurityUtils implementation. It really shouldn't be accessed inside of GUI code.
Instead, SecurityUtils.getSubject() should be used for everything related to the currently executing subject, aka 'user'. On Fri, Mar 27, 2009 at 11:21 PM, Ryan McKinley <[email protected]> wrote: > In an effort to answer a previous question -- how to get the current > SecurityManager in a WebApp, I stumbled into: > JSecurityFilter.SECURITY_MANAGER_CONTEXT_KEY > > It *seems* like a key in the servlet context for the Manager, but I don't > see it set anywhere and don't get any results with: > > WebApplication.get().getServletContext().getAttribute( > JSecurityFilter.SECURITY_MANAGER_CONTEXT_KEY ); > > > Am i missing something? > > Thanks again! > ryan >
