Hi Jason, Thanks for following up on this. Perhaps some dialogue will help us figure out the best path forward. Here are some questions and thoughts that come to mind.
Is this code in production anywhere? Who is the main target audience of the account-linking feature? What other use-cases might be covered by this functionality that would be of interested to the Jasig community, to Higher Ed, to CAS adopters generally? What is the motivation for seeing this code included in the Jasig distribution vs keeping it as an extension in a Galois github repo? Did this feature require any modifications to core CAS code/apis, or did it more or less fit into the existing APIs? If merged into CAS distribution would it be easy for it to be turned off by default? Easy for folks to exclude it? What are your thoughts regarding where this fits into the CAS roadmap based on the release strategy? https://wiki.jasig.org/display/CAS/CAS+Roadmap Are the normalized attributes returned in the CAS protocol payload? There has been a long and on-going discussion around rev'ing CAS Protocol doc to formally include attributes. This would normalize various ad-hoc methods and get the CAS clients to support it. I wonder how this fits in with that. If this is more of a CAS3 plug-in like the OpenID work that Jerome did, then it might be possible to take a similar path if you are committed to maintaining this going forward, and able to comply with Jasig licensing requirements (apache2, CLAs, etc). - http://www.jasig.org/licensing Best, Bill On Thu, Apr 12, 2012 at 7:07 PM, Jason Dagit <da...@galois.com> wrote: > We at Galois would really like to move forward with merging our CAS > additions into the mainline of CAS, in particular, the project funding this > effort is about to end and Jonathan and I will move to other projects. Once > that happens we can continue to do maintenance but our capacity for this > work will be much smaller than it is currently. > > Earlier this year, I posted our CAS modifications on github > (https://github.com/dagit/grid2-als) and shared the link here. I haven't > received any feedback on the code yet and we would really like to keep this > moving. Galois can continue to do maintenance and the ideal time for us to > work on this is now. > > What is the best way for us to move forward? The code is available on > github, but would a pull request against the CAS repository be more helpful? > We haven't tried our code recently with the latest version of the CAS > source, so it's possible we need to do some work there. > > We are also wondering if the refactorings in CAS 4 will remove the need for > some of the code we wrote to to be integrated directly into CAS. Could > someone who is experienced with the generalizations in CAS 4 help us > evaluate that? To help you understand how our modifications work, here is a > link to our documentation: > http://grid2.galois.com/release-2012-01-28/cas-als-configuration.txt > > Questions? Comments? Concerns? > > Thanks, > Jason > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@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
