Not sure i follow 100%, but, I think we might be mixing concerns here.

I'm guessing com.john.appone.Person is something application specific
right? and this is unrelated to your security session?

On Wed, Apr 6, 2016 at 11:03 AM, johnrellis <[email protected]> wrote:

> Hey folks,
>
> It looks as though "poor mans" Single Sign On is possible with Shiro using
> native sessions with Ehcache and Terracotta.
>
> This sounds good as all our apps are using Shiro so it is an avenue I would
> like to explore.  There is one problem though that is stopping me from
> implementing this solution.
>
> If I have two applications, AppOne and AppTwo
>
> What happens if AppOne store com.john.appone.Person in the session and
> AppTwo attempts to load that session?  My guess is there would be a class
> not found exception in AppTwo, would that be correct?
>
> If so, is there any way around this?
>
> I found a SO post which says to break up session but I'm not sure how
> possible this is.
>
> Many thanks,
> John
>
>
>
> --
> View this message in context:
> http://shiro-user.582556.n2.nabble.com/Questions-about-poor-mans-SSO-tp7581009.html
> Sent from the Shiro User mailing list archive at Nabble.com.
>

Reply via email to