Web Dispatcher -"Your session has timed out. Please log on again"

[Former Member]

Hello,

I have a web dispatcher in the DMZ configured for SSL and connected to backend J2ee CI + 2 java app servers. SSL is configured and working with verisign certs.

The problem is when we access the backend customer URL (via a re-direct in the web dispatcher) ...we do get the correct login page, however as soon as we type a user/password we immediately get "Your session has timed out. Please log on again."..

Now, I also have a re-direct going to the Netweaver Administration (NWA) using https....this works great. It is only with the customer url using xcm config that causes the error.

any ideas?

icm/server_port_1 = PROT=HTTPS, PORT=443, TIMEOUT=15, PROCTIMEOUT=45

icm/HTTP/redirect_0  = PREFIX=/, FROM=/marset, TO=/marset/init.do?scenario.xcm=marset (this is the problem re-direct)

icm/HTTP/redirect_1 =  PREFIX=/, FROM=/nwa,    TO=/nwa                                                  (this works fine for netweaver admin)

thanks,

Ld

[Former Member]

Hi,

I'm sorry but your redirection rules don't make any sense to me.

You don't need redirection rules to access the backend system.

Redirection rule are mostly used when you want to simplify an technical URL.

Regards,

Olivier

[Former Member]

Hi Olivier,

The redirection is simple now, since we are just testing for one customer...later each customer will type in the https://domain.com/CustomerName and we will re-direct them to the full URL (TO=/CustomerName/init.do?scenario.xcm=CustomerName)..this is for e-commerce.

What is interesting, is that if I use the web dispatcher server name INSTEAD of the domain name...it works...both for the re-direct as well.

example:

https://svrp000124ee.xwca.com/CustomerName (this is the web dispatcher hostname....this works and is re-directed to the full backend url.

https://ghoshealthcaretest.com/CustomerName (I get the re-direct to the backend j2ee server however as soon as I enter user/password on login page...the timeout 'error' occurs. One note, it does not even try to actually use the user/password....it just immediately produces the timeout message'.

thank you for any ideas .

Linwood

Message was edited by: Linwood Doty Update...I just tested with this re-direct and it works .. icm/HTTP/redirect_0  = PREFIX=/, FROM=/marset, TO=/marset/init.do?scenario.xcm=marset, HOST=eccuatj01, PORT=54201 when I specify the HOST it works, however we do not want to do that since we have several java app servers that need to be used via load balancing... So the question is what is wrong with this re-direct sysntax? icm/HTTP/redirect_0  = PREFIX=/, FROM=/marset, TO=/marset/init.do?scenario.xcm=marset

[Former Member]

This has been resolved....

As per note 791765, please set JSESSIONID.CookieDomain to "NONE"

and restart your J2EE engine.

Linwood