> 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: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
