Chris, Most CAS clients expect the ticket to be the ticket parameter. In CAS 3.1(which isn't out yet), you can define a "Service" which utilizes a different redirect URL, specifically for that one application. CAS 3.1 is still in the development stages though unfortunately.
-Scott On 6/11/07, Chris Krall <[EMAIL PROTECTED]> wrote:
Hello A vendor who is implementing a CAS client for us has asked that we rename the "ticket" parameter returned in the URL https://my.site.edu/cp/home/displaylogin?goto=https://my.site.edu/cp/cas/login?service=https://wiki.site.edu/bin/view https://wiki.site.edu/bin/view?ticket=jfijfjwefpwoejfo[wefjweofj since they already use a url parameter by that name for other functionality. I personally think if they wish to offer CAS they probably don't want to do it with the stipulation "but you have to change what you are doing", but that's just me. Is this something trivial or do all CAS clients expect the "ticket" parameter to be named as such? Please pardon my ignorance as I am filling in for someone on leave of absence. Thanks for any input -C _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
-- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
