Hi Ron,
         Can you please tell me one thing. In my case I am going to package the 
portlets in different war files as per the features. So my question is 
         1) when I deploy these war files in the portal server, do I need SSO 
integration if 
I need to authenticate user in all of the WARs. Assuming all the war files are 
deployed in the same tomcat.
         2) when I deploy these war files in the portal server, do I need SSO 
integration if 
I need to authenticate user in all of the WARs. Assuming all the war files are 
deployed in different  tomcat servers.


Thanks,
Alok.


-----Original Message-----
From: Ron Wheeler [mailto:rwhee...@artifact-software.com] 
Sent: Sunday, July 05, 2009 4:51 PM
To: Jetspeed Users List
Subject: Re: Can I have each portlet in different war

The  web pages in a portal contains a selection of portlets regardless 
of how you package up the webapps and once you are connected to a 
session you share the authentication and authorization for your session.
The portal page is selected based on your profile. The content of the 
page is assembled by Jetspeed based on your PSML files.

SSO is used to gain access to other people's web sites.

Ron


Alok Jain wrote:
> Hi,
>             Thanks for the reply. Also can you please confirm that I need to 
> integrate SSO like CAS with Jetspeed for the
> Seamless authentication of the users across all the web-apps.
>
>
> Thanks,
> Alok
>
> -----Original Message-----
> From: Ate Douma [mailto:a...@douma.nu] 
> Sent: Thursday, July 02, 2009 12:50 AM
> To: Jetspeed Users List
> Subject: Re: Can I have each portlet in different war
>
> Alok Jain wrote:
>   
>> Hi,
>>               Can I have  each portlet packaged in a different WAR and 
>> deployed in the same portal server.
>>     
> Sure, no problem.
> The portal maintains a registry through which webapp (WAR) a portlet is 
> deployed.
> One think to keep in mind however is that portlets bundled in one webapp do 
> have the advantage that they can share the same servlet session 
> and portlet session (APPLICATION_SCOPE). If you don't need that, deploying 
> all of them in separate webapps gives you the benefit of a very 
> fine-grained release/deployment life-cycle.
>
>   
>> Thanks,
>> Alok.
>>
>>     
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
>
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org

Reply via email to