There are many different design considerations that pertain to your own situation, This example is self-contained web application that shares Shiro security context with EJB security context. You will need to do more work and design to figure out how to extend this to client situation, as there are different levels of trust between client and server.
What I provided is a starting point, and an example of how to deal with sharing security context between EJB and Shiro. My situation (web server / app server communication) is not the same as yours ( client/server) You need some other way to push the security context around, as in my situation, the context just stays in the web server. I don't think there is an out-of-the-box solution for this. On May 27, 2014, at 12:48 AM, P82 wrote: > Thank you for your time. But I can't understand from links which you provide > what code must I use on client side and what code must I use on server side. > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Glassfish-4-EJB-Shiro-OSGI-standalone-client-tp7579977p7579979.html > Sent from the Shiro User mailing list archive at Nabble.com. >
