Mark, 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. -Scott On 10/15/07, Mark McCoy <[EMAIL PROTECTED]> wrote: > > Hey all, > > In case you may not have seen my posts earlier this month, we are trying > to get > our CAS 3.1 server to trust and/or proxy the tickets generated by an > older CAS > server that we are unable to modify or replace (it's built into some > prepackaged > software). Most of the time, the user will login to that software > first, so we > wish them to be then automatically logged into any application that the > CAS 3.1 > server protects. > > The solution proposed by this list and the (unofficial) support list for > the > other software was to proxy the tickets. The problem is that even after > digging > through various bits of documentation on the CAS wiki, I still have > absolutely > no idea of how the ticket proxying between 2 servers (and not > server->client) > really works or how to set it up! > > Please point me in the right direction to documentation or how-to's on > this subject. > > Thanks in advance! > Mark > > ---- > Mark McCoy > Enterprise Services (Unix Group) > Office of Information Technology > The University of Texas at San Antonio > (210) 458-5871 > _______________________________________________ > 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
