UWC - Invalid URL after a session timeout

Question

Using Communications Express 6.3 (122793-12), when a user's session times out their browers is redirected to:
http://my.server.com/base/UWCMain?op=logout
which generates a 404 File Not Found error. I believe the URL needs to be:
http://my.server.com/uwc/base/UWCMain?op=logout
Where can I set this?
Thanks,
Scott

Answer 1

Having a similar issue to the original poster, but not quite the same.
We've just upgraded to Messaging Server 6.3, with pretty much the latest
patch sets installed for the various components.
# imsimta version
Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 64bit)
libimta.so 6.3-6.03 (built 17:30:55, Mar 14 2008; 64bit)
Using Messaging SSO with the following configutil params,
local.webmail.sso.enable = 0
local.webmail.sso.singlesignoff = 1
local.webmail.sso.uwccontexturi = uwc
local.webmail.sso.uwcenabled = 1
local.webmail.sso.uwclogouturl = http://webmail.wright.edu/uwc/base/UWCMain?op=logout
CommExpress is installed on a separate server (Solaris9/Sparc). In our case thought when
a session times out, the URL that's presented is
https://base/UWCMain?op=logout
Note that I have ssl enabled for CommExpress. I initially I had the uwclogouturl set to use
https which resulted in the same url above which is missing the host information and leading
url path. I had just changed it this morning to see if the behavior would change with straight
http with no difference.
CommExpress is running under Sun Java System Web Server 7.0U3 B06/16/2008. I have a
similar setup in test with CommExpress running on the same server as the MTA and it works
ok there, just not in production on a separate server.
As things stand right now, once a session times out, a user has to shutdown their browser
to start a new CommExpress session.
I just put a call in to Sun, but wondering if anyone has run into this before?
Thanks.
Update: after talking with support, just realized I'm 2-3 revs behind on the latest UWC patch
(122793). Not sure how I missed this one. Looks like bug-id 6598975 patched in 122793-18 may
fix this one.
Edited by: john_meyers on Sep 2, 2008 10:58 AM