We are in the process of deploying a 3rd party application that authenticates against our 1.3 Shibboleth IDP. Our Shibboleth IDP uses our CAS server for its authentication (Tomcat using mod_auth_cas).
So we hoping a login to one of our in house CASified applications would result in an SSO experience with the 3rd party application. But this is not the case. No matter the order the applications are accessed the user is always prompted for credentials. The users don't like this especially since they get the exact same CAS login screen twice. I am not sure why we get this behavior, but I am not surprised either. What confuses me is that whether signing into our in house application or the 3rd party application the users browser is redirected to the CAS login screen. I thought this would be sufficient to enable SSO. Anyway I do understand Shib and CAS are 2 distinct SSO solutions so it is not surprising to get this behavior. Does anyone have any thoughts on this? Cheers, Bryan -- 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
