I agree with both of these points. I hope to attend ACAMP and will likely bring another developer or two with me in October. However, I'm also hoping that we'll have already made some good progress implementing parts of this by then, so I'm counting on online discussion to make sure we're going in the right direction.
Where can I look to find details about InCommon's LOA efforts? Also, is there any relevant documentation/discussion in the Shib community that we should take note of? -Nathan From: "<William G. Thompson>", "Jr." <wgt...@gmail.com<mailto:wgt...@gmail.com>> Reply-To: "cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org>" <cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org>> Date: Wednesday, August 1, 2012 8:03 PM To: "cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org>" <cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org>> Subject: Re: [cas-dev] Leveraging Renew for Multifactor Use Cases The level of thoughtful discourse on this subject is highly encouraging! :) Couple of things come to mind: * We would do well (at least for the HE/R&E communities) to make sure this effort syncs up well with InCommon's efforts on LOA and plays well with Shib, since the CAS/Shib combination is common deployment scenario in HE/R&E. (perhaps there's an opportunity at the Internet2 ACAMP in October for some f2f discussion on this topic) * "That could work great for clients that support the SAML ticket validation endpoint, but it might be nice to enhance the CAS protocol's XML to include metadata too." I suggest that it's not only nice, but that it should be a requirement. The LOA proposal in combination with the need for attributes and other minor additions provides enough justification for a rev of the CAS protocol doc. Best, Bill -- 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
