OK, if there is no interest currently to add generic attributes to the RegisteredService, one current solution for the extensions is to overload the meaning of "allowedAttributes" and use"attr:value" scheme. Works just fine.
Another lighter weight and much more flexible solution is to define all kinds of metadata in the separate config Map and store in in MongoDB as JSON documents per service. Might as well also implement storing the entire services reg. in MongoDB. We haven't implemented the latter yet, but when we do, we might consider donating it to CAS if there is enough interest ;-) Cheers, D. Sent from my iPhone On Feb 7, 2012, at 15:51, Marvin Addison <[email protected]> wrote: >> Unicon is collaborating with Columbia University on a Services >> Registry extension for Login Screen UI. > > The problem with these kinds of extensions is that they tend to be > suitable for a particular institution. I could get excited about an > ad-hoc system for extending the service registry to support arbitrary > attributes, but that's probably more work than it's worth to simply > develop a custom solution for one institution. > >> * Help URL and text > > FWIW, we used the description field to support this use case and set > escapeXml="false" for JSP output tags that displayed the field to > support rendering HTML content. > > M > > -- > 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 -- 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
