Derivation of Web UI: link in e-mail notices

Hi,

Customers are reporting that email links to work items as a result of
updates
are failing (timeout due to firewall constraints on our server). The
Web UI:
link looks like:

http://rtp-rtc10:9081/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/1058


The 9081 port apparently comes from the tomcat server.xml as that port
is
used for the license server clients to use, but it redirects to the
9443 port.

If one is firewall authenticated, the 9081 port works fine. Rather
than add
hundreds of users to the firewall access we got exceptions for the
9443 to
be 'world' accessible. I could open another exception request, but
wanted
to ask if there is another way to influence the construction of the
link.

Thanks,

Kevin

yzwkzfn wrote:

Hi,

Customers are reporting that email links to work items as a result of
updates
are failing (timeout due to firewall constraints on our server). The
Web UI:
link looks like:

http://rtp-rtc10:9081/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/1058


The 9081 port apparently comes from the tomcat server.xml as that port
is
used for the license server clients to use, but it redirects to the
9443 port.

If one is firewall authenticated, the 9081 port works fine. Rather
than add
hundreds of users to the firewall access we got exceptions for the
9443 to
be 'world' accessible. I could open another exception request, but
wanted
to ask if there is another way to influence the construction of the
link.

Thanks,

Kevin

Thanks,

I had come across that earlier. I have set to
https://hostname:9443/jazz

bpaserowrote:
yzwkzfn wrote:
Hi,

Customers are reporting that email links to work items as a result
of
updates
are failing (timeout due to firewall constraints on our server).
The
Web UI:
link looks like:


http://rtp-rtc10:9081/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/1058

The 9081 port apparently comes from the tomcat server.xml as that
port
is
used for the license server clients to use, but it redirects to the
9443 port.

If one is firewall authenticated, the 9081 port works fine. Rather
than add
hundreds of users to the firewall access we got exceptions for the
9443 to
be 'world' accessible. I could open another exception request, but
wanted
to ask if there is another way to influence the construction of the
link.

Thanks,

Kevin


This link is dependent on the public URI setting that you can
configure
in Admin Properties in the Web UI. I suggest you do that unless
already.