Yes, I suggest we target splitting the Service Management app for 4.0, as this would be consistent with the release strategy. The downside is wider scope for 4.0, but it looks like folks are available to get this done now, so I'd like to see it move forward. I should also say that we've seen lot a deployments lately forgo the SM altogether and go for the JSON file registry.
Jérôme, you could add this this to the Roadmap if you are willing to take it on. https://wiki.jasig.org/display/CAS/CAS+Roadmap Best, Bill On Sun, Sep 2, 2012 at 8:25 AM, Dmitriy Kopylenko <dmitriy.kopyle...@gmail.com> wrote: > As far as I know - no 3.6. Next major version will be labeled as 4.0. Anyone > correct me if I'm wrong. > > Cheers, > Dmitriy. > > Sent from my iPhone > > On Sep 2, 2012, at 6:35, "jleleu" <lel...@gmail.com> wrote: > >> Hi, >> >> I did some tests on this issue. I encountered many problems in the services >> management webapp : links are not working most of the time and I couldn't >> add a service. >> It's clearly due to the memory optimization which destroys web sessions. It >> triggers round-trips with the CAS server. By default, Spring security >> configuration for CAS always calls the default page : so you can almost >> never call add.html, you are redirected to manage.html. Moreover, as every >> action in the webpp triggers a CAS re-authentication, the requested page is >> saved and restored which cannot work for POST requests as Spring security >> only knows to restore GET requests. Every re-authentication on CAS server >> goes through the "redirect" stage in webflow which could not be used as a >> fallback solution. >> >> The memory optimization for CAS server is not compatible with the services >> management webapp. >> >> I start thinking about moving out the services management webapp and it will >> be a big change on source code (I will split cas-server-webapp into >> cas-server-webapp and cas-management-webapp), but also for CAS deployers and >> that's where I see the problem : they will need to add a new webapp with a >> specific configuration. Even if I'm very enthusiastic about this feature, I >> have to admit that it's too much for a minor version like 3.5.1. >> >> So I proposed to disable the optimization for 3.5.1 (pull request #118) and >> I plan to start my work on 3.6.0 by re-enabling this optimization and moving >> out the services management webapp. >> >> What's our planning for 3.5.1 / 3.6.0 ? >> >> Best regards, >> Jérôme >> >> -- >> You are currently subscribed to cas-dev@lists.jasig.org as: >> dmitriy.kopyle...@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: wgt...@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
