Honestly, our CAS configuration changes so infrequently that we don't even need to use a regular service registry; we just have our configs stored in the deployerConfigContext.xml file directly.
Chris >>> Jérôme LELEU<[email protected]> 07/26/15 9:08 AM >>> 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] 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
