|
Home > Archive > WebSphere Portal Server > June 2007 > WebSeal and Portal 6.0.1 Issues
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WebSeal and Portal 6.0.1 Issues
|
|
|
| We just installed and configured TAM/WebSeal and Portal 6.0.1. We are seeing an issue where everything works fine except the "Launch" menu and drag and drop portlets. The WebSeal server is not correctly changing the URLs for these items.
e.g. Our junction name is /wpsv6/. All the portal URLs are /wpsv6/wps/myportal etc... except in the new portal 6 dynamic functions such as the launch menu and the drag and drop portlet functionality. These items are returning links to /wps/myportal/.
The WebSeal server is not reverse proxying the URL to be /wpsv6/wps/myportal/ on these items.
I've enabled script-filtering on the WebSeal server, but that didn't make any difference. At this point I don't know what else to change.
Anyone else have similar issues, or know what else to configure to get this working? The InfoCenter documentation does not say much more about how to configure this.
thanks
| |
|
| I had the same issue - however, when I re-created the junction on WebSeal *without* the "-j" option it suddenly worked ... here is the command I used
pdadmin> server task default-webseald-my.hostname.domain create -f /portal -t tcp -h portal.server.domain -p 80 -A -F "/path/to/ltpa/key-file.key" -Z "ltpa key password"
But I still have create a junction mapping table in <pd-web-home>/www-default/lib/jmt.conf (same entry is in etc/webseald-default.conf and needs to be loaded within pdadmin (using server task default-webseal.... jmt load). the content of jmt.conf looks li
ke this (assuming yor junction is called /portal): /portal /wps/*
Good luck, Jürgen
|
|
|
|
|