For backwards compatibility, maybe the new protocol should be served from a new URL... something like this: /validate = CAS 1.0 /serviceValidate = CAS 2.0 /samlValidate = SAML (might need some updates) /serviceValidate4 = CAS 4.0 (if we want the new protocol number to match the CAS release number)
That way any client that wasn't yet updated could keep accessing the old 2.0 protocol at "/serviceValidate" and new clients could get all of the fancy new features at the new URL. Of course, someone can probably think of a better URL than "/serviceValidate4". :-) -Nathan On 9/18/12 10:46 AM, "Robert Oschwald" <robertoschw...@googlemail.com> wrote: >I can start working on a first draft for it. > >Is the CAS Protocol Specifications Scope for JA-SIG CAS Only or is it a >general spec (e.g. samlValidate in JA-SIG CAS, "destination" parameter in >rubyCAS). > >Robert > -- 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
