+1 separate project -1 removal
- The web app is protected but accessible (via a url in a browser) a JSON file would be less accessible. - The json file is much easier to corrupt, the UI can ensure data is correct Humans shouldn’t have to manage application data via file formats. At least you didn’t suggest XML, then it would have been -20. We use it a) to authorize services on our CAS installation and specify theme, b) to authorize attribute release for the various services. Dale From: Jérôme LELEU [mailto:[email protected]] Sent: Monday, 27 July 2015 2:08 a.m. To: [email protected] Subject: [cas-dev] Drop the management webapp 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 [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-dev -- 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-dev
