This is resolved. Not a configuration issue, but rather a coding issue. Part of the application allows a user with permissions to view/edit other users and there was sloppy handling between currentUser and the viewed user objects that caused the problem.
-- View this message in context: http://shiro-user.582556.n2.nabble.com/Issue-with-Shiro-authorization-getting-cleared-tp7140992p7142954.html Sent from the Shiro User mailing list archive at Nabble.com.
