The goal was to support all the obvious data that people relate to a service including contacts, keys, etc. It was mostly based off what all the options were for SAML meta data (since they pretty much include everything as an option).
The goal was to be more simplified though. I.e. a wizard/flow to register a service, generate the required keys, etc. then an administrator could enable/edit the submitted data. I had a basic (ugly) workflow going minus any emails/notification. We've made a decent number of changes so I'd be surprised if it still works out of the box :-) Cheers, Scott On Tue, Dec 27, 2011 at 5:01 PM, Marvin Addison <marvin.addi...@gmail.com>wrote: > > Not to sound like a broken record, but the CAS4 code base was working on > > (and had some support already) for this. > > > I thought most of the additional metadata was supporting SAML use > cases like signing and encryption. It's been a while, so perhaps a > brief outline will help guide us toward a more meaningful code review. > > Thanks, > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@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-dev
