Understanding shib-cas-authenticator

[Baci]

I've been looking to integrate my CAS (3.5.2) and Shibboleth. Unicon's
shib-cas-authenticator <https://github.com/Unicon/shib-cas-authenticator> looks
pretty cool but as I'm reading the documentation in the software
requirements section, I'm confused. If I have many services managed by CAS,
I'd need to deploy Shibb IDP in the servlet container of each server? Is
the "web resource protected by CAS (casauth)" any "casified" application?
We use an externally hosted learning management system, which currently is
a CAS managed service. I don't have access to the hosting server, If I
wanted to use the shib-cas-authenticator I'd need to put shibb-idp on that
box? Will I need to maintain many instances of the Shibb-IDP? Right now I'm
set up with CAS and Shibb in the same webapps dir on Tomcat. Thanks in
advance for any enlightenment you might be able to pass on.

-- 
  Chris Bacigalupo
*   Information technologies . Portal Administrator
*   + (218) 723-7083 + cbacigal at css.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131023/8ceda048/attachment.html