We utilize the management app for our CAS deployment. We have a clustered deployment and share administration of the registered services with about 10 admins who don't have direct access to the servers hosting CAS. We have also extended the registered service object to add on a few of our own customizations that we've added in to the management app (e.g. api key management for several apis we've added to CAS).
We would be fine if the management app was separated from core. But would prefer to still have a base management service somewhere we can extend instead of having to create our own from scratch. Sent from my phone. On Jul 26, 2015 10:08 AM, "Jérôme LELEU" <lel...@gmail.com> wrote: > Hi, > > The CAS service model has strongly evolved for the CAS server v4.1 and the > powerful new policies are hard to define through a UI. Maintining this > webapp requires a lot of work. > The default services registry is now based on JSON files which also makes > manual editing a lot easier. > > I'm in favor of dropping the CAS management webapp or maybe first moving > it into a separate project. > > I'd like to get feedbacks on this idea: do CAS deployers use it? How? > > Thanks. > Best regards, > Jérôme > > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > daniel.fr...@ccci.org > 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
