On May 16, 2007, at 10:36 AM, Mark McLaren wrote:
I checked the response I was getting from the AJAX requests using
Firebug and the requests were being redirected to the CAS login
screen.
I fixed my problem by adding "*.js" to the CAS filter so that when my
portlet page loaded an invisible "single sign on" occurs. As you
suggest, this appears to be piggy backing on the sso browser
session and
I imagine it is now passing additional cookie information that was not
there before so that now requests to the backend application actually
work! At least I think this is what is happening! :-/
Have you tested in IE? At least in IE6/Win I remember we had to do
some manual cookie maniputlation on the XMLHttpRequest due to the
different way IE handles cookie-scoping. I don't know if this is
still necessary in IE7...
Jason
--
Jason Shao
Application Developer
Office of Instructional & Research Technology
Rutgers University
v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED]
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
