Upgrade 3.7.1 to 3.9 - Session expired

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Upgrade 3.7.1 to 3.9 - Session expired

Thorsten Stumpf
Hi!

We are experiencing two problems on updating our 3.7.1 XForms to Orbeon
3.9.
The first is about expired sessions in portlet/embedded mode the other
is concerning an id-Attribute enforcing its' content to be a Boolean
value.

I will describe the two problems in two separate requests but I
definitely appreciate if you also have a look for the other mailing list
entry.

We have a PHP-based CMS which delivers our content. Orbeon is integrated
by an Apache AJP-proxy declaration.
The XForms applications are dynamically injected by CMS-/PHP-templates
which do a kind of proxy request on initialization:

The PHP-backend performs a parameterised request to the XForms
application (switching it to portlet mode) and injects the whole
returned HTTP response into the page frame delivered by the CMS.

For 3.7.1 this works perfect.
The injected HTML/JavaScript communicates with the AJP exposed orbeon
xforms-server (http://our.server/orbeon/xforms-server).
We didn't do anything special with JSESSIONID.

3.9 basically seems to do the same.
The whole form is rendered as before.

But as soon as a backend request is triggered the system throwed an
unspecified error.
We tried to fix that by parsing the JSESSIONID and setting it to the
proper value via the module/template delivering the page frame and
XForms HTML/JS body.
It is set (we checked) and has the value of the header.
Though the XForms throws an error again: Session expired.

Is there anything else to be set? What are the things we should keep an
eye on?
I saw another poster in the list with an similar problem - though we
don't use Liferay.

Thanks for your help in advance

JT


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade 3.7.1 to 3.9 - Session expired

Erik Bruchez
Administrator
JT,

It's likely that 3.7.1 did not check that the session was there, but
3.8 and 3.9 do.

The only thing to do really should be to map the session cookie properly.

We do something like this in the proxy portlet:

https://github.com/orbeon/orbeon-forms/blob/master/src/scala/org/orbeon/oxf/portlet/OrbeonProxyPortlet.scala#L217

And we do something similar with the TYPO3 extension:

http://wiki.orbeon.com/forms/doc/developer-guide/form-runner/typo3-extension

-Erik

On Tue, Apr 5, 2011 at 7:52 AM, Stumpf, Jens Thorsten
<[hidden email]> wrote:

> Hi!
>
> We are experiencing two problems on updating our 3.7.1 XForms to Orbeon
> 3.9.
> The first is about expired sessions in portlet/embedded mode the other
> is concerning an id-Attribute enforcing its' content to be a Boolean
> value.
>
> I will describe the two problems in two separate requests but I
> definitely appreciate if you also have a look for the other mailing list
> entry.
>
> We have a PHP-based CMS which delivers our content. Orbeon is integrated
> by an Apache AJP-proxy declaration.
> The XForms applications are dynamically injected by CMS-/PHP-templates
> which do a kind of proxy request on initialization:
>
> The PHP-backend performs a parameterised request to the XForms
> application (switching it to portlet mode) and injects the whole
> returned HTTP response into the page frame delivered by the CMS.
>
> For 3.7.1 this works perfect.
> The injected HTML/JavaScript communicates with the AJP exposed orbeon
> xforms-server (http://our.server/orbeon/xforms-server).
> We didn't do anything special with JSESSIONID.
>
> 3.9 basically seems to do the same.
> The whole form is rendered as before.
>
> But as soon as a backend request is triggered the system throwed an
> unspecified error.
> We tried to fix that by parsing the JSESSIONID and setting it to the
> proper value via the module/template delivering the page frame and
> XForms HTML/JS body.
> It is set (we checked) and has the value of the header.
> Though the XForms throws an error again: Session expired.
>
> Is there anything else to be set? What are the things we should keep an
> eye on?
> I saw another poster in the list with an similar problem - though we
> don't use Liferay.
>
> Thanks for your help in advance
>
> JT
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

RE: Re: Upgrade 3.7.1 to 3.9 - Session expired

Thorsten Stumpf
That where the examples I was looking at before I wrote the code and
before I even thought to post here...
Though it seems to work now.

It seems there was still an old JSESSIONID cookie stored in the CMS
request objects handler which was used instead of the new generated one
- maybe because it was more specific with the contained path setting...
So this one was used instead and that resulted in a session expired
error.

Thanks for your help!

Cheers

JT


> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Erik
> Bruchez
> Sent: Wednesday, April 06, 2011 8:08 AM
> To: [hidden email]
> Subject: [ops-users] Re: Upgrade 3.7.1 to 3.9 - Session expired
>
> JT,
>
> It's likely that 3.7.1 did not check that the session was there, but
> 3.8 and 3.9 do.
>
> The only thing to do really should be to map the session cookie
properly.
>
> We do something like this in the proxy portlet:
>
> https://github.com/orbeon/orbeon-
>
forms/blob/master/src/scala/org/orbeon/oxf/portlet/OrbeonProxyPortlet.sc
ala#

> L217
>
> And we do something similar with the TYPO3 extension:
>
> http://wiki.orbeon.com/forms/doc/developer-guide/form-runner/typo3-
> extension
>
> -Erik
>
> On Tue, Apr 5, 2011 at 7:52 AM, Stumpf, Jens Thorsten
> <[hidden email]> wrote:
> > Hi!
> >
> > We are experiencing two problems on updating our 3.7.1 XForms to
> > Orbeon 3.9.
> > The first is about expired sessions in portlet/embedded mode the
other

> > is concerning an id-Attribute enforcing its' content to be a Boolean
> > value.
> >
> > I will describe the two problems in two separate requests but I
> > definitely appreciate if you also have a look for the other mailing
> > list entry.
> >
> > We have a PHP-based CMS which delivers our content. Orbeon is
> > integrated by an Apache AJP-proxy declaration.
> > The XForms applications are dynamically injected by
CMS-/PHP-templates
> > which do a kind of proxy request on initialization:
> >
> > The PHP-backend performs a parameterised request to the XForms
> > application (switching it to portlet mode) and injects the whole
> > returned HTTP response into the page frame delivered by the CMS.
> >
> > For 3.7.1 this works perfect.
> > The injected HTML/JavaScript communicates with the AJP exposed
orbeon

> > xforms-server (http://our.server/orbeon/xforms-server).
> > We didn't do anything special with JSESSIONID.
> >
> > 3.9 basically seems to do the same.
> > The whole form is rendered as before.
> >
> > But as soon as a backend request is triggered the system throwed an
> > unspecified error.
> > We tried to fix that by parsing the JSESSIONID and setting it to the
> > proper value via the module/template delivering the page frame and
> > XForms HTML/JS body.
> > It is set (we checked) and has the value of the header.
> > Though the XForms throws an error again: Session expired.
> >
> > Is there anything else to be set? What are the things we should keep
> > an eye on?
> > I saw another poster in the list with an similar problem - though we
> > don't use Liferay.
> >
> > Thanks for your help in advance
> >
> > JT
> >
> >
> > --
> > You receive this message as a subscriber of the [hidden email]
> mailing list.
> > To unsubscribe: mailto:[hidden email]
> > For general help: mailto:[hidden email]?subject=help
> > OW2 mailing lists service home page: http://www.ow2.org/wws
> >
> >


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: RE: Re: Upgrade 3.7.1 to 3.9 - Session expired

Erik Bruchez
Administrator
Cool! -Erik

On Wed, Apr 6, 2011 at 9:59 AM, Stumpf, Jens Thorsten
<[hidden email]> wrote:

> That where the examples I was looking at before I wrote the code and
> before I even thought to post here...
> Though it seems to work now.
>
> It seems there was still an old JSESSIONID cookie stored in the CMS
> request objects handler which was used instead of the new generated one
> - maybe because it was more specific with the contained path setting...
> So this one was used instead and that resulted in a session expired
> error.
>
> Thanks for your help!
>
> Cheers
>
> JT
>
>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]] On Behalf Of Erik
>> Bruchez
>> Sent: Wednesday, April 06, 2011 8:08 AM
>> To: [hidden email]
>> Subject: [ops-users] Re: Upgrade 3.7.1 to 3.9 - Session expired
>>
>> JT,
>>
>> It's likely that 3.7.1 did not check that the session was there, but
>> 3.8 and 3.9 do.
>>
>> The only thing to do really should be to map the session cookie
> properly.
>>
>> We do something like this in the proxy portlet:
>>
>> https://github.com/orbeon/orbeon-
>>
> forms/blob/master/src/scala/org/orbeon/oxf/portlet/OrbeonProxyPortlet.sc
> ala#
>> L217
>>
>> And we do something similar with the TYPO3 extension:
>>
>> http://wiki.orbeon.com/forms/doc/developer-guide/form-runner/typo3-
>> extension
>>
>> -Erik
>>
>> On Tue, Apr 5, 2011 at 7:52 AM, Stumpf, Jens Thorsten
>> <[hidden email]> wrote:
>> > Hi!
>> >
>> > We are experiencing two problems on updating our 3.7.1 XForms to
>> > Orbeon 3.9.
>> > The first is about expired sessions in portlet/embedded mode the
> other
>> > is concerning an id-Attribute enforcing its' content to be a Boolean
>> > value.
>> >
>> > I will describe the two problems in two separate requests but I
>> > definitely appreciate if you also have a look for the other mailing
>> > list entry.
>> >
>> > We have a PHP-based CMS which delivers our content. Orbeon is
>> > integrated by an Apache AJP-proxy declaration.
>> > The XForms applications are dynamically injected by
> CMS-/PHP-templates
>> > which do a kind of proxy request on initialization:
>> >
>> > The PHP-backend performs a parameterised request to the XForms
>> > application (switching it to portlet mode) and injects the whole
>> > returned HTTP response into the page frame delivered by the CMS.
>> >
>> > For 3.7.1 this works perfect.
>> > The injected HTML/JavaScript communicates with the AJP exposed
> orbeon
>> > xforms-server (http://our.server/orbeon/xforms-server).
>> > We didn't do anything special with JSESSIONID.
>> >
>> > 3.9 basically seems to do the same.
>> > The whole form is rendered as before.
>> >
>> > But as soon as a backend request is triggered the system throwed an
>> > unspecified error.
>> > We tried to fix that by parsing the JSESSIONID and setting it to the
>> > proper value via the module/template delivering the page frame and
>> > XForms HTML/JS body.
>> > It is set (we checked) and has the value of the header.
>> > Though the XForms throws an error again: Session expired.
>> >
>> > Is there anything else to be set? What are the things we should keep
>> > an eye on?
>> > I saw another poster in the list with an similar problem - though we
>> > don't use Liferay.
>> >
>> > Thanks for your help in advance
>> >
>> > JT
>> >
>> >
>> > --
>> > You receive this message as a subscriber of the [hidden email]
>> mailing list.
>> > To unsubscribe: mailto:[hidden email]
>> > For general help: mailto:[hidden email]?subject=help
>> > OW2 mailing lists service home page: http://www.ow2.org/wws
>> >
>> >
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws