Hi there, I'm developing a portal application using Pluto 1.1.0-beta2
embedded inside a glassfish (version 9.1) javaee application server.
Embedding of the portlet container was done following same instructions than
embedding pluton with Tomcat and it has been almost successfully.

 

The portal application is deployed and running, portlets are invoked through
Pluto Container using the pluto-portal-driver provided with the
distribution.

 

The problem are the http sessions of the portal webapp (Top Level) and the
portlet applications because if a user that was previously authenticated
against the portal realm closes his http session only just the portal webapp
http session is invalidated.

 

The same problem arises when the first user is authenticated and newer one
starts another session, at the portlet applications the current user is the
first who was authenticated and the newer one is ignored.

 

Is this an issue related to glassfish?

 

Does anyone know how to propagate the invalidating of the portlet app http
sessions from the portal webapp?

 

Regards

Alonso

Reply via email to