So, I think I discovered the issue. Turns out I was running my service as my own user rather than as root. When I tried to authenticate, I was using the root id and credentials. The RMI Exception being thrown appears to indicate that
1) there was a security exception (unable to authenticate) which threw a ShiroAuthentication exception 2) RMI was unable to find that class on the client and actually rethrow it on the client side. The auth exception was happening because I was not running as a root user, so I had no access to the password database for any users other than myself. When I tried to use my own username and password, it worked fine. The RMI exception was happening because (as mentioned above) the ShiroAuthException class was not found on the client, and the client was configured to not allow classes to be downloaded from the server - the default configuration. Interesting shiro problem. Anyone know what the best practice is for something like this? Thanks, John -- View this message in context: http://shiro-user.582556.n2.nabble.com/AuthenticationException-no-security-manager-RMI-class-loader-disabled-tp7580372p7580373.html Sent from the Shiro User mailing list archive at Nabble.com.
