Reading work items from jazz.net via plain Java API possible?
Hello,
for some analysis purposes we would like to read work item data from https://jazz.net/jazz.
When trying to connect to the mentioned server using the RTC Eclipse client (provided as part of the RTC release) a connection cannot be established.
I have to say that we are sitting behind a corporate firewall/proxy.
Now I am wondering whether our proxy is the problem or jazz.net.
Can you please help me?
Thank you
showing 5 of 6
show 1 more comments
|
Be the first one to answer this question!
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.
Comments
I cannot connect either. I believe I did in the past but am not totally sure.
Same for me. I also think that it was working some time but is no more.
I notice that some time ago the jazz.net project areas were configured to require a second authentication (if I log in to the forum already, I have to log in again to see the work items), and this may indicate that the infrastructure has changed, and accessing from the RTC Eclipse client is no longer possible. Whether it's intentional, I don't know.
I think the effect you see is from JAS OICD . The environment is clustered and has JAS set up as far as I know.
I know it used to work. I also saw in a recent setup in 6.0.4 with JAS OICD the issue that if the first part of the proxy url is the same for JAS and CCM (e.g. https://jazz.net/ccm --> https://jazz.net/oidc/jazzop/endpoint...) then Eclipse would refuse connection. This got fixed in 6.0.5 and works for us now.
Any stuff in the Eclipse log file? If you stumble upon an "RSA premaster secret error" then take a look at https://developer.ibm.com/answers/questions/206325/how-to-fix-this-ssl-error-javaxnetsslsslkeyexcepti.html
But my gut feeling says it is none of the easy solutions.
I've never been able to connect to jazz.net via Eclipse outside of the IBM firewall, but I guess I just wasn't trying hard enough (:-). I'm guessing the answer is "it was never supposed to work", but I'll ask around and see. You can of course access it via HTTP, but I'm guessing you have a bunch of code already in Eclipse that works, and would rather not recode it against the HTTP API.