> shouldn't we revert to the original CAS > 2.0 endpoint and create this new v3 endpoint right now in a 4.0-RC3 ?
+1 > And if our strategy is to make CAS clients adapt to new endpoints (and not > the opposite), couldn't we add also to this new v3 endpoint the > authentication attributes required for remember-me (isFromNewLogin, > authenticationDate, maybe a lastUpdatedDate...) Seems equivalent to I asked about a while back w/r/t proxy, which was rejected. I'm not opposed to meaningful protocol v3 enhancements that make sense, but it's probably true that it's not consistent with our release policy if we're targeting these changes for 4.0. I'm not one to let policy get in the way of positive change; I'm open to tweaking policies if we wanted more flexibility now and going forward. M -- 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
