Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

IS OSLC workshop example compatible with CLM3.0.1.*?

Hi CLM experts,

I have been trying the OSLC workshop example, particularly for RM part but having problem with running examples (3 and 4) successfully. The issue seems to be authorisation failure and it throws with the following error message from RM example 4.

>> POST https://clm.com:9443/jts/j_security_check
    - Server: Apache-Coyote/1.1
    - Content-Length: 0
    - Date: Tue, 02 Oct 2012 23:51:18 GMT
3/10/2012 09:51:18 org.apache.http.impl.client.DefaultRequestDirector handleResponse
WARNING: Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="Jazz"}
org.apache.http.client.HttpResponseException: Unauthorized
    at net.jazz.oslc.consumer.examples.Example04.getServiceProvider(Example04.java:303)
    at net.jazz.oslc.consumer.examples.Example04.run(Example04.java:79)
    at net.jazz.oslc.consumer.examples.Example04.main(Example04.java:108)

I have tried with different instances of CLM but results are same for v3.0.1. However, this works just fine on CLM4.0.  Can anyone advise me what I could possibly miss here?

Thank you in advance,

0 votes

Comments

Hello Charlie
I don't understand why you are having trouble because the examples we have available work with RRC v3.0.1 and NOT v4.0.  So, I am confused why it is not working for you unless you have mixed up which CLM server you are actually accessing with the example code.  Can you double check what CLM server version you are actually connecting to when trying to run Example04?

We are working on putting out a version of the workshop that works for v4.0.

Hi Rosa,

Thank you for your response. I have definitely checked multiple times with RRC 3.0.1 and even with different installations, but the results were identical. I have tried with CLM 4.0 to find out any difference but strangely it worked just fine. The version I tried was 3.0.1.3 and 3.0.1 and my client is experiencing the same issue so wondering. Any advise for digging it further would be great.

Thank you,

Hi is there any update on this?

@rnaranjo
Is there a way to get access to the version of the java code that works for RRC v3?
Can I interest anyone with debug code?
I have the same problem.

Thanks,



One answer

Permanent link
Thank you Rosa. Charlie probably didn't phrase the issue adequately. 

We have solved the issue and I would like to post the response for any others that may encounter this problem.

We have set up separate URLs for our applications so that jts server is https://jts.apps and rm server is https://rm.apps.  

In order to use the workshop examples, you need to perform a replace on the rm server URL to be the jts URL when you are accessing the catalog, but when you come down to the next level, you need to leave the rm server URL.
System.out.println(">> Service Providers Catalog: "+catalogURI);
            catalogURI = catalogURI.replaceAll("rm.apps", "jts.apps");

0 votes

Comments

liesa,
the above explanation was not enough to explain, at least to me, what the problem was and what the resolution was exactly.  Could you provide more details and try one more time to explain the workaround?

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 10,938
× 516

Question asked: Oct 02 '12, 7:56 p.m.

Question was seen: 5,444 times

Last updated: Mar 05 '13, 10:15 a.m.

Confirmation Cancel Confirm