app-main.war's acting as a portal, making requests on behalf of the end user directly to app1.war and app2.war, is a proxy CAS n-tier delegated authentication use case.
On Wed, Mar 6, 2013 at 12:53 PM, W.Alphonse HAROUNY <wharo...@gmail.com>wrote: > Hi, > > I have a main application (app-main.war) acting as a portal towards other > applications (app1.war, app2.war, ..). > All these applications were CASsified. > > - The user is triggering app-main.war thru REST calls. > In this module, the CAS was integrated using the jasig > AuthenticationFilter. > - Then according to the user's request, a new REST request is sent by > "app-main.war" towards the target service (app1.war, app2.war, ...) . > > My question is about which is the appropriate implementation to let the > whole works : > 1/ Is it by integrating "cas-server-integration-restlet" api into the > target sevices (app1.war, app2.war, ...) ? > 2/ Or is it better to declare "app-main.war" as a CAS Proxy towards > (app1.war, app2.war, ...) > and let it access the services ? > 3/ And why ? > > Thank you. > Alf. > ------------------------------ > View this message in context: Which is the appropriate implementation: > CAS-Proxy or > CAS-Rest<http://jasig.275507.n4.nabble.com/Which-is-the-appropriate-implementation-CAS-Proxy-or-CAS-Rest-tp4658466.html> > Sent from the CAS Users mailing list > archive<http://jasig.275507.n4.nabble.com/CAS-Users-f255676.html>at > Nabble.com. > > -- > You are currently subscribed to cas-user@lists.jasig.org as: ape...@unicon.net > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
