We did it usually the Java Client, protecting /cru/* and /login/ with the Authentication filter and then all other pages with the validation filter. I started a page in Confluence (which has almost no information at this moment):
http://www.ja-sig.org/wiki/display/CASC/Fisheye+and+Crucible We're using a beta of the JASIG CAS Client for Java. So what I actually want to do is upgrade it to the latest client. When I do that I'll post the directions. Until then the best answer I can give is we used the Java client protecting the above urls. We also enabled the setting of the remote user so that Crucible could find the username. Hope that helps somewhat. -Scott On Dec 10, 2007 10:23 PM, Parker Grimes <[EMAIL PROTECTED]> wrote: > I noticed JA-SIG has CASified their Fisheye / Crucible instance. I tried > searching for info on how to do it but couldn't find anything. Can someone > point me in the right direction? > > Thanks, > Parker Grimes > Southern Utah University > > _______________________________________________ > 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
