> On Nov 20, 2014, at 1:20 PM, Milt Epstein <[email protected]> wrote:
> 
> But it does sound like I'm in a bit of a lurch trying to use CAS 4.0
> and the JSON service registry.  You mention that Monolithic cas-addons
> is still supported for CAS 3.5.1+ -- but, to clarify, I assume that
> support ends with 4.0?

Correct. That’d be only supported for 3.x line of CAS

> 
> Your pointer to a sample YAML service definition file is helpful --
> although I do have a few questions about what some of the
> parameters/attributes mean.  Is there documentation/a guide for that
> somewhere?

There is no documentation yet. I’m hoping to put it out there some time next 
week to make it more clearer. Before then, to clear up some confusion, this 
implementation uses SnakeYAMl library (a standard, “de-facto” YAML library in 
the Java world), as well as YamlTag library to create short, DSL-like tags for 
internal objects used to create instances: https://github.com/xrrocha/yamltag 
<https://github.com/xrrocha/yamltag>

So current implementation define the following tags (the ones that start with 
‘!’):

!serviceWithAttributes - maps to 
net.unicon.cas.addon.registeredservices.DefaultRegisteredServiceWithAttributes

!regexServiceWithAttributes - maps to 
net.unicon.cas.addon.registeredservices.RegexRegisteredServiceWithAttributes

!defaultAttributeFilter - maps to 
org.jasig.cas.services.support.RegisteredServiceDefaultAttributeFilter

!regexAttributeFilter - 
org.jasig.cas.services.support.RegisteredServiceRegexAttributeFilter

As CAS 4.1 introduces more collaborating classes, there will be more of these 
DSL tags. Of course all of this will be documented.
Everything else are standard reg svc properties.


> 
> 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/micro-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/micro-addons/src/main/webapp/WEB-INF/spring-configuration/servicesRegistry.xml
 
<https://github.com/UniconLabs/simple-cas4-overlay-template/blob/micro-addons/src/main/webapp/WEB-INF/spring-configuration/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 [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to