Thanks for your prompt response. We are working on SAAS model, the services consist of multiple web applications. Multiple combinations of the applications serve multiple clients (who are the Identity Providers). The services of the applications are also consumed by internal customers (Service Providers itself). There are consumers who home institution or IDP may be OPEN Id provider. Hence we have consumers/users from local home institution, clients from different domains and end user from Open Id. Currently these group of applications achieve SSO through CAS for the internal customers and achieve cross-domain SSO through custom built Assertion Consumer Services. We have plans to support Open Id users too. Shibboleth IDP will be more likely to simulate our client IDP. I understand if we use Shibboleth SP we will be able to easily federate our services, supporting multiple clients and both SAML1 and 2 assertions.
Thanks & Regards, Gokula -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Friday, April 16, 2010 7:53 PM To: [email protected] Subject: Re: [cas-user] request.getRemoteUser() returns null in CASSHIB > 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 -- 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
