Hi Fernando, The old client library isn't being actively maintained, so I suppose there's some danger that there will be an issue in it that you wish were fixed and little in the way of community and momentum for making that happen. On the other hand, it's free and open source software -- there's absolutely nothing stopping you from forking it into say GitHub and doing whatever you need to do to it.
The new client library is actively maintained and includes features not present in the older CAS client library, such as support for reading attributes via SAML 1.1 and handling single sign-out callbacks. Newer versions of the CAS server speak the same CAS2 protocol that the older version of the CAS Java client library speaks. CAS servers should be entirely interoperable -- that's the point of the documented CAS protocol. As you've observed, old CAS client libraries should have no problems interacting with shiny new CAS server instances. If you don't need the new features and are happily CASified with the older client library, I wouldn't feel any rush to update these existing applications. Kind regards, Andrew On Jan 28, 2012, at 5:48 AM, Fernando Correa wrote: > Hi guys! > > In my enviroment, we've implemented cas 2.0.12 since 2006. The client that > we've been using is 2.0.11. Now, we are moving to cas server 3.3.5 and client > 3.1.10. Many casified applications couldn't update the client. We tried to > use client 2.0.11 with server 3.3.5 and it worked. > > My question is. Is there any danger to use this client version? What are the > benefits of using the new client version? > > Thanks in advance! -- 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
