Hi, Resuming this thread : in that case, shouldn't we revert to the original CAS 2.0 endpoint and create this new v3 endpoint right now in a 4.0-RC3 ?
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...) Best regards, Jérôme 2013/11/12 Misagh Moayyed <mmoay...@unicon.net> > +1 > > -Misagh > > -----Original Message----- > > From: Marvin Addison [mailto:marvin.addi...@gmail.com] > > Sent: Wednesday, November 06, 2013 10:13 AM > > To: cas-dev@lists.jasig.org > > Subject: Re: [cas-dev] CAS Protocol v3 Status > > > > > Current endpoints: > > > /validate - CAS 1.0 protocol > > > /serviceValidate & /proxyValidate - CAS 2.0 protocol > > > > > > Proposed endpoints: > > > /v3/serviceValidate % /v3/proxyValidate - CAS 3.0 protocol? > > > > +1 > > > > Arguably a win/win solution. New endpoints offer the opportunity to > provide > > CAS 3 protocol features that make most sense (i.e. formal support for > multi- > > valued attributes) going forward while ensuring adequate backward > > compatibility with existing clients. > > > > M > > > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: > > mmoay...@unicon.net To unsubscribe, change settings or access archives, > see > > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > lel...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- 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
