Gokula posted to the casshib list and I have responded to him there, but
I wanted to respond re: What's CASSHIB for?
I developed CASSHIB for a very specific reason: I didn't want developers
on my campus that need to federate their applications to have to go
through the process of setting up their own Shibboleth service
providers. With CASShib the developers on my campus can just CASify
their apps and have easy federation.
The role of CASShib is to gateway the authentication credentials between
Shib and the app. It's more or less, from the client's perspective,
converting the Shibboleth protocol to the CAS protocol so that a more
developer-friendly client can be used. CASShib is more of a replacement
for the Shib SP than it is for the IDP (although the SP still needs to
be set up once for the CASShib server).
Marvin Addison wrote:
Trying to convert J2EE Web Application (myapp) as federated service using
Shibboleth SP, CASSHIB and Shibboleth IDP.
I think we need a high-level description of what you're doing and why
you need CASShib in the solution. With a Shibboleth IDP and SP, you
have all the tools you need to federate your application. Typically
CASShib replaces the Shib IDP in the mix, answering authentication and
attribute assertions (my limited understanding). What is the role of
CAS here?
M
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
