On 03/08/13 03:41, Jeff Abernathy wrote:
Hello everyone,
I know this is an ongoing discussion on here, and there are multiple
solutions available. But, I'll ask the question anyway...
We have a very new CAS instance setup to run a very few applications.
And we now are getting requests to do a SAML(2) provider also, leading
me to Shibboleth. There seem to be multiple ways to do a CAS/Shib
integration. Given that we have done quite a bit of work to get CAS
socialized, and I would like to keep CAS in front of the user, if you
had to integrate the two in my shoes, which method would you use?
The ones I have found so far are
The RemoteUser solution:
https://wiki.jasig.org/display/CASUM/Shibboleth-CAS+Integration
The SSO-CAS solution:
https://wiki.shibboleth.net/confluence/display/SHIB2/SSO-CAS+Login+Handler
And finally a shib-cas-authenticator:
https://github.com/Unicon/shib-cas-authenticator
I'm sure each has its merits. I would like the most seemless
integration between the two possible from the end user perspective.
Thanks for the opinions and suggestions.
Jeff Abernathy
We've been using
https://wiki.jasig.org/display/CASUM/Shibboleth-CAS+Integration
(read until "Shibbolize CAS") for the last few years without any problem.
Users either from casified application or shibbolized applications
are redirected to a single CAS login page.
The last option https://github.com/Unicon/shib-cas-authenticator
seems also interesting but I've not tested it.
G
--
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
