Hi Jerome,
  Thanks for the clarification.

  I believe the "ServiceUrlAuthenticationManagerImpl" strategy can still
serve the need.

Regards,
Franklin

On Wed, Feb 29, 2012 at 1:21 PM, jleleu <[email protected]> wrote:

> Hi Franklin,
>
> 1) I don't mean two CAS servers : I said two SSOs for simplification but
> it is more a conceptual vision of your system.
> I think your problem is more on accessing to app3 from app1 or app2 than
> on enabling SSO between all your applications.
>
> 2) With one CAS server, if you authenticate to access to app1 or app2, you
> can access to app3 but also to app2 or app1 : it's the principle of SSO :
> authenticate once and then get access to other applications participating
> in the SSO.
> That's why I talk about customization to prevent users from app1 to access
> to app2 and prevent users from app2 to access to app1.
>
> Best regards,
> Jérôme
>
> --
> 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

Reply via email to