team Central Event log

JanVdP wrote:

I am running my jazz server on port 9444. When I try to click on a
link in my event log, I get the 'Login Required' alert, but this uses
the default 9443 port and as a consequence I can not log in.

1. Can I change the port number to 9444 somewhere so the Login
Required makes use of it??

2. Is this expected behavior? I would suspect the login required alert
would use the current connection to validate against the jazz server.
What in case of two open connections to different servers??

There's a publicUri property on the server that informs feeds and other URIs
created in the client as to what URI to use as the host/authority/jazz context.
Using the Admin Web UI, verify that that property's value is also using the
same port number.

--
Todd Lainhart
Jazz Repository/Foundation Team

I have modified the publicUri root to the follow value:

https://localhost:9444/jazz

After restart from both client and server, the problem remains.

JanVdP wrote:

2. Is this expected behavior? I would suspect the login required alert
would use the current connection to validate against the jazz server.
What in case of two open connections to different servers??

This is not the expected behavior. The feed entries that the client are reading
contain absolute URIs that are generated by the server. If your server is has
been modified to listen/run on port 9443, and you've modified the server.webapp
property ("public URI root"), then I would expect the URIs embedded in the feed
to have the correct port number.

Is it possible that you have some entries cached on the client prior to your
port change? Can you do some client gesture to create a new feed entry (e.g.
create a new workitem), and see if you see the same behavior?

--
Todd Lainhart
Jazz Repository/Foundation Team

New elements can be accessed while old entries indeed keep their old address (previous port number)...

I was thinking that when a user clicks on a feed item, the server connection would be dynamically loaded...