On Tue, Apr 16, 2013 at 9:21 AM, Marvin S. Addison <[email protected]> wrote: >> I tend to agree with the move towards a more functional architecture, >> however breaking ticket encapsulation this late in the release cycle >> is worrisome. > > > We're revving the CAS protocol in this release, and you're concerned about > this? It's a minor implementation detail by comparison. Moreover, major > version releases are for big changes, which puts this fully in the proper > scope. If that one line change breaks something, we'll consider > alternatives. I trust Jérôme to handle it competently, and I hope you will > work with us on getting an important and oft-requested feature into the the > next release.
The CAS protocol rev is simply catching up to current practice...nothing revolutionary there. My concern is more about available cycles to properly evaluate the change given we're so late in the release cycle. As we all know SLO has its issues[1], and even though front-channel SLO is in the SAML spec, I'm not aware of any actual production deployments. Anyone else? I would prefer to see actual production deployments of the proposed feature before complecting the Jasig distribution with it. Best, Bill [1] https://wiki.shibboleth.net/confluence/display/SHIB2/SLOIssues > > > 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
