If its in its own web app, then their sessions shouldn't collide?
On Tue, Sep 4, 2012 at 10:42 AM, Marvin Addison <marvin.addi...@gmail.com>wrote: > > So I proposed to disable the optimization for 3.5.1 (pull request #118) > > I would like to offer an alternative solution: > > https://github.com/Jasig/cas/pull/119 > > I would argue that the optimization is beneficial for 99.9% of tickets > issued. My simple fix tags service manager sessions in a way that > suppresses termination by the flow listener. My testing shows it's an > adequate fix, and this way we can benefit from a valuable optimization > while not breaking service manager. > > I'd also like to point out that divesting the service manager into a > separate webapp will not necessarily solve this issue. In the common > deployment scenario where both CAS and service manager are deployed to > the same servlet container, the same issue could arise. The fix above > is therefore valuable now and going forward. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
