portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor" <da...@bluesunrise.com>
Subject Re: WebPagePortlet and cookies
Date Tue, 06 Nov 2001 19:32:35 GMT
Paul, I 'll try to check the session management  stuff in by the weekend.
In testing it handles multiple sessions and cookies, need to test out that
redirect scenario below

David

----- Original Message -----
From: "Laura lega" <spanishisotta@libero.it>
To: "Jetspeed Developers List" <jetspeed-dev@jakarta.apache.org>
Sent: Tuesday, November 06, 2001 10:51 AM
Subject: Re: WebPagePortlet and cookies


> Hello again.
> We need to use cookies to mantain the session of a client with a  server
> through different calls to pages. I'm going to explain.
>
> We have the following:
>     - IBM Domino Go WebServer
>     - Websphere Application Server
>
> Jetspeed is installed on Websphere Application Server. Our application,
that
> contains an authentication process is hosted on Domino Go WebServer.
> We want to use our application like a part of a portal built with
Jetspeed.
> In order to do this, we tried to use the WebPagePortlet to call the first
> page of the application.
> Our client sends a request for the first page of the application to
> WebPagePortlet  on Jetspeed. The WebPagePortlet tries to get the page. The
> WebServer recognizes the client has not logged in and sends Jetspeed a
page
> for authentication. Jetspeed forwards this page to the browser.
>
> The user fills in the form and sends the page (this time) directly to the
> WebServer.
> The user has logged in.
>
> Now the browser asks for another page of the application on the Webserver.
> It does it through the WebPagePortlet.  The WebPage Portlet contacts the
> WebServer to collect that page and the WebServer doesn't recognize the
> requester and again sends the authentication page.
> This shouldn't happen.
>
> The problem is that when communication is directly between browser and
> server, the browser receives the cookie the server uses to recognize the
> client. After this, client and server go on exchanging the cookie during
> their communication. The client can request many pages and it will be
> authentified by the cookie.
>
> When Jetspeed is in the middle, with the WebPagePortlet, cookies get lost.
>
> I understand that when Jetspeed is in the middle, it will receive cookies
by
> the browser.  It should forward them to the webServer.
> In our situation:
>     - serverA --> IBM Domino Go WebServer + our web application
>     - serverB --> Websphere Application Server + Jetspeed
>
> considering all requests (inclusive those that will be managed by the
> Websphere Application Server) will be directed to the Web Server, I don't
> know if the browser, after authentication will get the authentication
cookie
> "marked" as ServerA or ServerB.
>
> Furthermore, which cookies will Jetspeed get from the client? Those marked
> as ServerA or those marked as ServerB?
>
> I'm not sure I'm explaining myself. If not, please ask.
>
> Thanks,
>     Laura
>
>
>
>
>
> ----- Original Message -----
> From: "Paul Spencer" <paul@mikon.com>
> To: "Jetspeed Developers List" <jetspeed-dev@jakarta.apache.org>
> Sent: Tuesday, November 06, 2001 1:39 PM
> Subject: Re: WebPagePortlet and cookies
>
>
> > Laura,
> > Their is currently an effort underway to extend the WebPagePortlet that
> > will include cookies support.  Below are some questions and comments.
> > Since the developer doing the work also reads this mailing list, you
> > answers may help in his effort.
> >
> > 1) As a general rule a web server, jetspeed in this case, will only
> >    receive cookies that is sets.  So the cookies set by Yahoo are not
> >    visible to Jetspeed
> >
> > 2) How do you intend on using the Cookie support?
> >     o Are the cookies user specific?
> >     o Will the user access the URL, as define in the WebPagePortlet,
> >       directly and via the WebpagePortlet?
> >
> > Paul Spencer
> >
> > Laura lega wrote:
> > >
> > > Hi everybody!
> > > I need to extend WebPagePortlet in order to deal with cookies.
> > >
> > > I understand the portlet that retrieves a HTML page should receive
> > > cookies sent by the browser and deliver them to the server so
> > > that the server can recognize the client.
> > >
> > > I believe the way is:
> > > 1) the portlet gets the cookies from the browser by calling the
> > > getCookies method on the Request object.
> > >
> >
> > > Here I have the first problem: how do I retrieve the Request object?
> > > I saw I can get it from the RunData object by  writing:
> > >     runData.getRequest( )
> > > ....but where do I get the RunData object corresponding to my portlet?
> > >
> > > 2) the portlet sends the cookies to the server while retrieving the
web
> page by calling:
> > >
> > >         HttpURLConnection  pageConn = (HttpURLConnection)
> pageUrl.openConnection();
> > >         pageConn.setRequestProperty("Cookie", cookie);
> > >         InputStream    is = pageConn.getInputStream();
> > >
> > > Thanks in advance,
> > >     Laura
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> <mailto:jetspeed-dev-help@jakarta.apache.org>
> >
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:jetspeed-dev-help@jakarta.apache.org>
>
>



--
To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>


Mime
View raw message