Unfortunately, we are still at 3.4.2 and have frequent additions to the CAS registry - however, we could insert them via the Database until moving to the JSON registry .. honestly, by the time I find a way to migrate our unusual authentication policies from this version to even 3.5.2, you all will have a different solution anyhow. We can adjust.
Linda Linda Toth University of Alaska - Office of Information Technology (OIT) - Identity and Access Management 910 Yukon Drive, Suite 103 Fairbanks, Alaska 99775 Tel: 907-450-8320 Fax: 907-450-8381 linda.t...@alaska.edu | www.alaska.edu/oit/ On Mon, Jul 27, 2015 at 5:34 AM, Jérôme LELEU <lel...@gmail.com> wrote: > Hi, > > It's already possible to reload the services periodically from database > for example, but not when it's defined in the Spring context. > > With the new JSON services registry, the services are automatically > created, updated and deleted. > > Best regards, > Jérôme > > > 2015-07-27 15:20 GMT+02:00 Ourada, John <jour...@depaul.edu>: > >> Ours changes very infrequently also, but has started changing more now >> that we have external apps that need to authenticate. Those require a >> manual entry in the deployer config file. It requires a manual restart of >> CAS application to reload them. I haven’t looked at 4.1 yet, but it would >> be nice if the app would look for updated service registry files and >> reloaded them periodically. >> >> >> >> -john >> >> >> >> *From:* Christopher Myers [mailto:cmy...@mail.millikin.edu] >> *Sent:* Monday, July 27, 2015 7:16 AM >> *To:* cas-user@lists.jasig.org >> *Subject:* Re: [cas-user] Drop the management webapp >> >> >> >> 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<lel...@gmail.com> 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 cas-user@lists.jasig.org as: >> cmy...@mail.millikin.edu >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-user >> >> >> >> -- >> >> You are currently subscribed to cas-user@lists.jasig.org as: >> jour...@depaul.edu >> >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-user >> >> -- >> You are currently subscribed to cas-user@lists.jasig.org as: lel...@gmail.com >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-user >> >> > -- > You are currently subscribed to cas-user@lists.jasig.org as: ltt...@alaska.edu > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to cas-user@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-user
