> 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.
Wonder if it's a service registry issue, e.g. singleSignOn=false? You might turn up the m-a-c debug logs and post those as a next step. I'm quite certain you can get single sing-on working; we have seamless CAS-Shib SSO using the method described at https://wiki.jasig.org/display/CASUM/Shibboleth-CAS+Integration, which is conceptually similar. 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
