This happens whenever code is executed for which Shiro has not been initialized properly beforehand.
We had some issues with Primefaces Push (atmosphere), too, so we simply wrote our own websocket code for push functionality. Research on the internet brings up statements, that Shiro would break websockets thereby causing atmosphere not to work, but our code clearly proves that Shiro does *not* break websockets - which is why we believe the problem lies with atmosphere. Anyway, here is an example we use to initialize Shiro for Apache Camel - you probably need to do something similar when you initialize atmosphere (we use pax shiro CDI integration https://github.com/ops4j/org.ops4j.pax.shiro): String iniFile = // loaded from database Ini ini = new Ini(); ini.load(iniFile); IniSecurityManagerFactory factory = new CdiIniSecurityManagerFactory(ini, manager); SecurityManager securityManager = (SecurityManager) factory.getInstance(); SecurityUtils.setSecurityManager(securityManager); -- View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-and-Primefaces-Push-atmosphere-tp7580831p7580832.html Sent from the Shiro User mailing list archive at Nabble.com.
