.. following up. I also tried to do: ThreadContext.bind(SecurityUtils.getSubject());
in my Controller at the time of login but that seems to have no effect (at least in my case). Same error (subject authenticated = false). Given the user is authenticated (SecurityUtils.getSubject().isAuthenticated() = true) and a row is created in DB for that user with fields say username, sessionid, blob session. Where is Shiro looking for (retrieving information from) SecurityUtils.getSubject().isAuthenticated() during subsequent readSession/update calls? Is it the database? If so which field in the DB or is it the ThreadContext/sessionid information? Please let me know how I can make my thread/session/subject persistent for shiro readSession/update calls (when this information is already stored in the RDBMS). -- View this message in context: http://shiro-user.582556.n2.nabble.com/Unable-to-implement-create-read-update-session-tp5183219p5188196.html Sent from the Shiro User mailing list archive at Nabble.com.
