There are a few differences between the native JSON service registry and that of CAS: http://jasig.github.io/cas/development/installation/Service-Management.html#persisting-registered-service-data
The native implementation assumes that configuration files are stored in a directory, which it will use to recursively look for service definitions. Each service definition is stored inside a single file. The format and syntax of these files are also different because they closely mimic the CAS object model for services. This provides the flexibility for CAS to change its model as needed without having to change the implementation to support the new changes. Rather than individual bits and pieces that would control a service behavior, we have introduced types to combine those pieces. At the same time, this also means it might be more difficult to understand the file if you were going to change this manually. (Note the @class elements in the snippet above) CAS itself periodically reloads its service definitions regardless of the backend implementation, so that should also work with the JSON option. Opinions vary here but if you'd rather use an interface to change service definitions then the syntax/format would be less important since you're no longer hand massaging the configuration files. In the past, the interface has gotten less use than hoped I suppose, because it's not as user friend and intuitive as most folks would like. It's been a while since it's gotten any attention. If you need to expose administrative privileges to a group to allow for service changes, or if you wish to apply those changes without having direct access to the CAS host (or wherever the files are hosted), then the management interface is for you. We plan to work on the interface next to allow support for the full range of features CAS now provides over its service configuration and this, along with the native json impl should become available in the next 4.1 release. > -----Original Message----- > From: mepst...@gwork254.lis.illinois.edu > [mailto:mepst...@gwork254.lis.illinois.edu] On Behalf Of Milt Epstein > Sent: Monday, December 1, 2014 11:51 AM > To: cas-user@lists.jasig.org > Subject: Re: [cas-user] json services registry for cas > > I can add some here, as someone who is using the Unicon JSON Service > Registry with our current CAS installation (version 3.4.12), and who plans > to use the Unicon YAML Service Registry with the new version of CAS > (version 4.0) -- I'm still working on getting the new version completely > installed and configured, so it's not yet in production usage, but the > YAML Service Registry is set up and ready to go. > > 1. The JSON Service Registry has worked very well for us. The JSON format > is clear and straightforward, although you do have to watch out for things > like braces/brackets and commas. And it's nice to be able to quickly edit > a file to make changes -- to add or remove a service, to change what > attributes a service receives. Additionally, the changes are picked up > pretty much immediately. (Perhaps I should add that our usage is pretty > low volume in number of authentications and number of services, and also > pretty basic in what the services > require.) > > 2. Getting the YAML Service Registry going was even easier (once the > issues mentioned in this thread were cleared up). Besides the service > registry file itself, there was a dependency to add to the pom.xml file, > and just one configuration file. The YAML format is even easier than the > JSON format -- perhaps that's helped by the fact that I've been doing a > lot of Python programming lately -- spacing/indentation matters, and > basically no braces/brackets or commas. > > 3. I'm not really familiar with many of the features/attributes available > in the YAML registry -- mostly because our usage is fairly basic and > hasn't needed it. I may look into this further at some point, especially > if more documentation for it is added. > > 4. I don't know how the native JSON implementation will vary from the > existing Unicon JSON/YAML versions. Certainly in some sense it will be > easier to get it going, with it being native, and no outside > dependencies/configuration to add. But maybe some things about it will > make the Unicon versions more desirable -- simplicity/clarity of the > config file, available features. I also don't know when the CAS version > that includes the native JSON Service Registry will be release. > > 5. We have not had the need to make management of the service registry > available through the web, or to persist it to databases or LDAP. So I > haven't dealt with any of the functionality or configuration in this area. > If you do have such needs, that might push you one way or the other. > > Milt Epstein > Applications Developer > Graduate School of Library and Information Science (GSLIS) University of > Illinois at Urbana-Champaign (UIUC) mepst...@illinois.edu > > > On Mon, 1 Dec 2014, John Gasper wrote: > > > Linda, > > > > I believe that CAS 4.1 will have a native JSON implementation of the > > service registry. It isn't the same as Unicon's. If you need some of > > the flexibility that Unicon's JSON Service Registry added (if it isn't > > in the native implementation) then you'll want to look into the YAML > > add-on that Dmitriy referenced below. > > > > Thanks, > > John > > > > On 11/26/14 11:14 AM, Linda Toth wrote: > > > I am still following this thread, and also am interested in what CAS > > > developers have to say on the subject, especially since I was > > > directed to JSON as a solution. > > > > > > 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 > > > <mailto:linda.t...@alaska.edu> | www.alaska.edu/oit/ > > > <http://www.alaska.edu/oit/> > > > > > > > > > On Fri, Nov 21, 2014 at 11:07 AM, Dmitriy Kopylenko > > > <dkopyle...@unicon.net <mailto:dkopyle...@unicon.net>> wrote: > > > > > > Just an FYI - I just released the 1.0.0-GA version and put the > > > documentation out > > > there: > > > https://github.com/unicon-cas-addons/cas-addon-yaml-services-registr > > > y/blob/master/README.md > > > > > > Have a great weekend. > > > > > > Dmitriy. > > > > > >> On Nov 20, 2014, at 7:01 PM, Dmitriy Kopylenko > > >> <dkopyle...@unicon.net <mailto:dkopyle...@unicon.net>> wrote: > > >> > > >> Glad that worked for you. It doesn't reload periodically, but on > > >> demand when the config file is changed. Look at the beans config > > >> that I referenced earlier. The entire config for this machinery > > >> is there. > > >> > > >> Cheers, > > >> D. > > >> > > >> Sent from my iPhone > > >> > > >>> On Nov 20, 2014, at 18:51, Milt Epstein <mepst...@illinois.edu > > >>> <mailto:mepst...@illinois.edu>> wrote: > > >>> > > >>> Thanks, that did the trick -- I was able install and use the > > >>> cas-addon-yaml-service-registry package via a dependency in my > > >>> pom.xml > > >>> file. The main problem was that I had used 1.0.0-M1 as the > version > > >>> (that was previously on the package's web page, but looks like > you > > >>> updated it to 1.0.0-RC1). > > >>> > > >>> And looks like it's automatically set up to reload periodically. > Is > > >>> that controlled by these parameters in cas.properties: > > >>> > > >>> # Service Registry Periodic Reloading Scheduler > > >>> # service.registry.quartz.reloader.startDelay=120000 > > >>> # Reload services every 2 minutes > > >>> # service.registry.quartz.reloader.repeatInterval=120000 > > >>> > > >>> (I didn't uncomment these, so it must be using default > > >>> values.) > > >>> > > >>> And for the core CAS devs, can you address these questions?: > > >>> > > >>>>> Other questions: I assume the CAS-integrated JSON service > > >>>>> registry is > > >>>>> not available for version 4.0, just 4.1? And when is 4.1 due > for > > >>>>> release? Is there a candidate ready to be tried now? How > > >>>>> close to > > >>>>> being ready to go is it? > > >>>> > > >>>> This is the question for core CAS devs ;-) > > >>> > > >>> Thanks. > > >>> > > >>> Milt Epstein > > >>> Applications Developer > > >>> Graduate School of Library and Information Science (GSLIS) > > >>> University of Illinois at Urbana-Champaign (UIUC) > > >>> mepst...@illinois.edu <mailto:mepst...@illinois.edu> > > >>> > > >>> > > >>>> On Thu, 20 Nov 2014, Dmitriy Kopylenko wrote: > > >>>> > > >>>>> On Nov 20, 2014, at 1:20 PM, Milt Epstein > > >>>>> <mepst...@illinois.edu <mailto:mepst...@illinois.edu>> wrote: > > >>> [ ... ] > > >>>>> But more importantly, it's still not clear how to > > >>>>> use/integrate the > > >>>>> cas-addon-yaml-service-registry package. Can I put a > > >>>>> dependency for > > >>>>> it in my pom.xml? I tried something for that, and it didn't > work. > > >>>>> Can I download it and put it into my maven overlay? I tried > > >>>>> downloading the master zip, and tried to build that (using > > >>>>> gradlew?), > > >>>>> separately, but it failed. > > >>>> > > >>>> Here’s an example of how to use it (version 1.0.0-RC1 is > > >>>> available in Maven central since yesterday): > > >>>> > > >>>> > > >>>> https://github.com/UniconLabs/simple-cas4-overlay-template/blob/m > > >>>> icro-addons/pom.xml#L62 > > >>>> <https://github.com/UniconLabs/simple-cas4-overlay-template/blob/ > > >>>> micro-addons/pom.xml#L62> > > >>>> > > >>>> > > >>>> https://github.com/UniconLabs/simple-cas4-overlay-template/blob/m > > >>>> icro-addons/src/main/webapp/WEB-INF/spring-configuration/services > > >>>> Registry.xml<https://github.com/UniconLabs/simple-cas4-overlay-te > > >>>> mplate/blob/micro-addons/src/main/webapp/WEB-INF/spring-configura > > >>>> tion/servicesRegistry.xml> > > >>>> > > >>>> Note that this config element > > >>>> <cas-external:yaml-services-registry/> assumes the default > > >>>> location to be: /etc/cas/servicesRegistry.yml Just put the file > > >>>> there and you should be good to go. > > >>>> > > >>>>> > > >>>>> Other questions: I assume the CAS-integrated JSON service > > >>>>> registry is > > >>>>> not available for version 4.0, just 4.1? And when is 4.1 due > for > > >>>>> release? Is there a candidate ready to be tried now? How > > >>>>> close to > > >>>>> being ready to go is it? > > >>>> > > >>>> This is the question for core CAS devs ;-) > > >>>> > > >>>> > > >>>> -- > > >>>> You are currently subscribed to cas-user@lists.jasig.org > > >>>> <mailto:cas-user@lists.jasig.org> as: mepst...@illinois.edu > > >>>> <mailto:mepst...@illinois.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 > > >>> <mailto:cas-user@lists.jasig.org> as: dkopyle...@unicon.net > > >>> <mailto:dkopyle...@unicon.net> > > >>> 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 > <mailto:cas-user@lists.jasig.org> as: ltt...@alaska.edu > <mailto: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: > > > jgas...@unicon.net 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: > > mepst...@illinois.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: > mmoay...@unicon.net 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
