> Hmm, interesting; is this just an exercise in seeing whether or not it could > be done
I certainly approached it like an exercise. > are there plans to make it so functional as to negate the need to run a > separate CAS server if you already have shibboleth deployed? Depends on functionality. I'm within striking distance to make it compatible with a strict interpretation of the CAS v2 protocol document, so I plan to do that by end of year. As I mentioned integration with the Shib attribute engine is pretty powerful and interesting, and I believe it's feasible and will investigate as development on IdPv3 progresses. There's a lot of active work on the attribute engine at present, so I have to let that settle a bit before diving in. Additionally, I'd like to target compliance with the CAS protocol 3.0 spec which is still settling down, so there's ample reason to take a break until Q1/Q2 2014 on that part. I'm fairly certain the SLO feature of the Jasig CAS server will be difficult to implement and I haven't even really analyzed the requirements or seriously considered an implementation strategy. I should note that I have absolutely no support for this endeavor from Virginia Tech or anyone else. I took it on as an interesting and challenging side project. I convinced the Shib dev team that there could be benefits for both the Shib project and to the larger Higher Ed IDM community if the work should pan out. I think it's fair to say the work has panned out; where it goes from here beyond what I outlined above I can't say at present. 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-user
