[cas-dev] RE ST API returning TGT

[Scott Battaglia]

We return it in the Location header because we're giving you the fully
constructed URL of where the newly created object resides.  That's from what
I can tell, the "standard" way of doing it.  And by standard, I mean, the
way everyone else recommends doing it. :-)  The difference between the TGT
and the ST responses is that the TGT refers to a new resource that has been
constructed and can be accessed via a URL.  The ST doesn't have that.
You're essentially just being returned a token identifier that you pass to
an application.

BTW, in case you hadn't noticed, we patched the TRUNK with the fix for the
incorrect URL being sent back in the Location header.
-Scott

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia


On Thu, Sep 25, 2008 at 8:15 PM, dale77 <Dale.Ogilvie at trimble.co.nz> wrote:

>
> Hello,
>
> The current CAS REST api returns the TGT in the location header of the
> response. Can the TGT also be returned in the response body?
>
> It seems inconsistent to me how the TGT comes back in the location header,
> while an ST is returned in the response.
>
> The advantage of returning the TGT also in the response body, is that it is
> more accessible. I am currently involved with an actionscript (flash)
> implementation which cannot access response headers easily (if at all).
>
> Thoughts?
>
> Dale
> --
> View this message in context:
> http://www.nabble.com/REST-API-returning-TGT-tp19680442p19680442.html
> Sent from the CAS Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20080926/6f0fbbbd/attachment.html