CASifying FishEye / Crucible
Scott Battaglia
scott.battaglia at gmail.com
Tue Dec 11 08:20:53 EST 2007
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 <grimesp at suu.edu> 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
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
--
-Scott Battaglia
LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20071211/5b3d4ae6/attachment.html
More information about the cas
mailing list