Its not an official part of the CAS protocol. It was included as "service" when CAS3 was written (6 years ago) because it was a common extension. I can't speak for why RubyCAS-client chose to use "destination" and not "service".
Cheers, Scott On Mon, Apr 16, 2012 at 2:37 PM, Jonathan Windle < jonathan.win...@bellevuecollege.edu> wrote: > Hello, > > I'm looking for information about how "official" and widely the service > parameter is used with /logout. We enable this feature in our CAS > implementation by setting the followServiceRedirects property to true for > the LogoutController defined in cas-servlet.xml (http://goo.gl/JLz9c). Up > until this point I have found this feature to be pretty well supported by > most CAS clients and plug-ins that we have implemented. > > Currently we are implementing the Canvas LMS by Instructure and it being a > Ruby on Rails product they use RubyCAS-Client to support CAS. > > The problem we are having is that RubyCAS-Client returns the redirect url > to /logout in a destination parameter not as a service parameter (Look > under "Defining a 'logout' action" at > https://github.com/rubycas/rubycas-client). > > So at this point I'm kind of wondering why the CAS specification ( > http://www.jasig.org/cas/protocol) doesn't define a parameter for > redirect on logout and why RubyCAS-Client seems to think that the parameter > name should be destination vs service. > > I would also be interested in knowing what's involved in making /logout > understand what to do with the destination parameter. > > Thanks, > Jonathan > -- > You are currently subscribed to cas-user@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to cas-user@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-user
