[cas-dev] JA-SIG CAS Java Client 3.0.0-m1 Released
Scott Battaglia
scott_battaglia at rutgers.edu
Thu Jun 22 23:54:09 EDT 2006
We're definitely looking into it. I don't want to rush to any decision
though about it as it would be a major extension to the CAS protocol (or
replacement) that we'd have to live with for a while :-D
As we're moving towards the end of the 3.0.X line (most likely), 3.1
would most likely be the CAS version that introduced parts of a new
protocol. Summarizing the ideas set forth so we can start to
investigate them seems like a good idea.
-Scott
Stephen A. Cochran wrote:
> On Jun 15, 2006, at 3:30 PM, Scott Battaglia wrote:
>
>
>> We are looking for early feedback and feature requests. Note that
>> although M1 uses Spring for configuration, there is only one class
>> that
>> actually has a Spring dependency. If anyone is interested in
>> contributing an alternate configuration, please do so.
>>
>> Upon GA release, this CAS Java Client will be integrated with the next
>> release of Acegi Security for Spring.
>>
>> Also, we're still looking for contributors for updating other CAS
>> clients. Feel free to contact us on the developers list if you'd like
>> to help out!
>>
>
> This is somewhat general client, but now is as good a time as ever.
> With more client work going on now that the 3.0 server is out, I
> think adopting a standard way to deal with extending the
> cas:SucessfulAuthentication message with additional attributes would
> be really useful. The goal here is to avoid having every site that
> wants to modify the response also have to dig through client code as
> well.
>
> I think that a decision on a direction might be enough impetus to
> make it happen. I'd be happy to summarize the ideas proposed earlier
> and hopefully it wouldn't take more than a conference call to choose
> a standard.
>
> Thoughts?
>
> Steve Cochran
> Dartmouth College
>
>
>
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>
More information about the cas-dev
mailing list