Scott, This seems fairly relevant to the problem I'm having. I'm resurrecting a posting from Oct of this year that was asked on the list ( http://tp.its.yale.edu/pipermail/cas/2007-October/006408.html ).
>You can make the new CAS server a client of the old one. There are two ways >to do that: > >1. Utilize the ValidationFilter in the cas client to validate a ticket if >one exists and then set the remote user. You can then use the >PrincipalBearing* support in CAS 3.1 to obtain the Principal from the Remote >User. > >2. Write custom Actions for the login flow / AuthenticationHandlers to >detect a ticket and construct appropriate credentials and have an >AuthenticationHandler able to validate the ticket. Can you dumb it down for us cas newbies? I've got my CAS server (3.1.1rc2 I think) deployed. How can it validate tickets coming from applications that the user is using in the old service? E.g. A person has logged into uportal behind a cas 2 server, and I would like the links that are behind the cas 3 server (on another domain) just to continue as if the user has already been validated. The tickets are not passed to me - there exists a cookie for the old domain as CASTGC - do I have to relax security on that cas implementation (and if so....where?) so that it makes the cookie available to my new cas server? Or, do proxy tickets come into play here? Regards, Chris -- Christopher Brooks Research Assistant, ARIES Laboratory Email: [EMAIL PROTECTED] Web: http://www.cs.usask.ca/~cab938 Mail: Mr. Christopher Brooks, MSc Department of Computer Science 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
