Hi Steinar,
The reason of hard to scale your application is session is been put in jvm. You can try to take session out of jvm into some sort of database or cache like EhCache, memcached, Redis. If you put session in Redis, you can try my project https://github.com/alexxiyang/shiro-redis . That might be easier for you to migrate session into Redis. ------------------ ???? ------------------ Original ------------------ From: "Brian Demers"<brian.dem...@gmail.com>; Date: Wed, Nov 14, 2018 02:17 AM To: "dev"<dev@shiro.apache.org>; Subject: Re: "Poor man's SSO", howto...? You would need to use something like EhCache or Hazelcast (or define your own cache impl) Does that help? On Tue, Nov 13, 2018 at 1:14 PM Steinar Bang <s...@dod.no> wrote: > >>>>> Brian Demers <brian.demers-re5jqeeqqe8avxtiumw...@public.gmane.org>: > > > Take a look at > > > https://shiro.apache.org/session-management.html#SessionManagement-SessionClustering > > But these techniques are typically tied to applications running on the > same > > domain. > > Thanks! :-) > > All of my applications are running in the same domain, on the same > server, and actually in the same VM (inside an apache karaf instance). > > But if I understand things correctly, for this to work, I need to have a > SessionDAO that persists sessions and is reachable from multiple > webapps? > > Is there a SessionDAO available that will work for multiple local > webapplications and doesn't require something like ecache or terracotta? > (something that works on the local file system, perhaps..?) > > Thanks again! >
