Even though I don't have a vote that counts, but I'll throw it out there for the record. +1 for the separate, modern web app for managing registered services, possibly supporting different back-ends for service registry storage e.g. RDBMS, MongoDB, flat JSON file, etc. It'd be benefitial that CAS itself would expose RESTful resources for registered services management, so all kinds of different clients could be built on top - official CAS web app, CLI clients, native mobile clients (imagine a nice iOS or Android apps for managing services registry!), etc.
Extracting services management UI piece also would have a side benefit of having "leaner & cleaner" CAS core. Cheers, Dmitriy. On Thu, Aug 30, 2012 at 7:10 AM, jleleu <lel...@gmail.com> wrote: > Hi, > > So disappointing ! > If I understand well, you can login, but your changes are lost. It's > strange though as I don't see where the webflow (and web session > destruction) comes into play when adding / editing services. > > I'll do some tests... > > I see two solutions right now : > - use an action to delete web session when in "redirect" stage in web flow > (first proposal I made in the pull request) > - extract the services management webapp out of the CAS server, as Scott > suggested. I'm +1 on this solution. I'm willing to work on that. > > 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: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
