> I'm in line with Robert, we should finish the spec (and the CAS server > 4.0.0) ASAP. I'd prefer we start a new CAS 3.1 revision to receive > enhancements.
I'm fine with waiting for a 3.1 spec for new features as long as it happens relatively soon. > There are several other things that could go also in a future revision : > - multi-values attribute (CAS-1283, > https://groups.google.com/forum/?fromgroups#!topic/jasig-cas-user/Ir9rcCuPgz4) We need to discuss this further. If you are saying that the present behavior of 4.0 RC2 is to deliver multi-valued attributes as [a, b, c, d], then there's more work to be done. That format clearly is not what phpCAS expects. If that format works with the Java CAS client, then we need to file an improvement issue for one of them to ship around the same time as 4.0 final. > About testing, I think the RCx and GA are made for that as the CAS server > always responds in a CAS3 protocol way. I've made tests for the Java CAS > client and it works. Glad to hear we have some integration test coverage, but there's more to be done. It's becoming clear to me that we need to cover additional clients (phpCAS, mod_auth_cas, .NET), and I would argue that it should happen during the RC phase and _before_ we ship GA. I'll be able to commit to some testing toward the latter half of this month. 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-dev
