It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,886

question asked: Nov 21 '08, 8:49 a.m.
question was seen: 4,225 times
last updated: Nov 21 '08, 8:49 a.m.

Related questions

team Central Event log

0
Jan Van de Poel (241●32●16) | asked Nov 21 '08, 8:49 a.m.
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??

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Todd Lainhart (406●1●1) | answered Nov 21 '08, 10:28 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
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
0
permanent link
Jan Van de Poel (241●32●16) | answered Nov 21 '08, 11:50 a.m.
I have modified the publicUri root to the follow value:

https://localhost:9444/jazz

After restart from both client and server, the problem remains.
0
permanent link
Todd Lainhart (406●1●1) | answered Nov 21 '08, 5:18 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
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
0
permanent link
Jan Van de Poel (241●32●16) | answered Nov 24 '08, 5:26 a.m.
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...

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.