And I just want to also clarify one bit - the proposal is not to entirely “abandon” the management UI, but to move it out of the CAS core repository into its own project, with its own release cycle.
> On Jul 27, 2015, at 10:30 AM, Jérôme LELEU <[email protected]> wrote: > > Hi, > > The proposed alternative with the server CAS v4.1 is to manually edit your > JSON services: add a JSON file to add a service, change a JSON file to update > a service, delete a JSON file to remove a service... > > Fairly basic, but it might be sufficient for most needs. > > Thanks. > Best regards, > Jérôme > > > 2015-07-27 16:27 GMT+02:00 Tom Poage <[email protected] > <mailto:[email protected]>>: > > > On Jul 26, 2015, at 7:08 AM, Jérôme LELEU <[email protected] > > <mailto:[email protected]>> wrote: > ... > > I'd like to get feedbacks on this idea: do CAS deployers use it? How? > > We were hoping to start using the registry as a means/layer of controlling > who can use of CAS, with UI being a self-service component for CAS clients. > > Let's say the UI is dropped. What alternatives are in use for CAS clients to > register their services? Does it have approval workflow? Etc. > > Thanks! > Tom. > -- > You are currently subscribed to [email protected] > <mailto:[email protected]> as: [email protected] > <mailto:[email protected]> > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > <http://www.ja-sig.org/wiki/display/JSG/cas-user> > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
