Hi,

I want to create a "Tested by" link from an RTC Work tem to a RQM Test Case. The cross server connection is established and the two Project Areas are linked.

From RQM it is no problem to link to an RTC Work Item or to a RRC Requirement. But when I try to create a new link from the RTC Work Item I get following error message:

Problems loading the service document containing the picker information. Problems acquiring the remote service document
The URI "https://RQM:9443/jazz/oslc_qm/contexts/_FRIgoAqCEd-aguIqCpJqmg/services.xml" has no OAuth authorization information associated to it.

Why can't I create the "tested by" link from the RTC Work Item?

Regards, Martin

I've managed to recreate the same problem with the same error message:

Problems loading the service document containing the picker information. Problems acquiring the remote service document
The URI "https://rqm:9443/jazz/oslc_qm/contexts/_2Cmw8BroEd-XyYW9i2_nhw/services.xml" has no OAuth authorization information associated to it.

I've checked the URI and it resolved OK with a download of services.xml. When I inspected the xml however I noted that all the tags contained malformed URL's, for example (errors in bold):

https://https://rqm:9443/jazz:9443/jazz/_ajax-modules/com.ibm.rqm.planning.TestPlanPicker?projectAreaName=MILO%20-%20Quality%20Manager

I removed the bold entries and manually copied the URL into an address bar and this resolved successfully. This shows that the service links are not resolving but doesn't resolve the issue.

As a result work items cannot link to test cases through RTC (both eclipse & web) but i've managed to achieve the reverse and provide some links through RQM.

I also suspect this has a knock on effect with Build Integration between RQM & RTC which we've also failed to set up. RTC Build Integration always exits (or times-out) with "Failed to Connect to Server", even after following the help instructions for RQM "build integration" to the letter.

Our suspect is the RQM installation, but numerous re-installs for us simply haven't resolved the issue.

I ran into the same issue:
"Problem creating a back link in New Requirement: The URI "https://rrc-server:443/rdm/resources/rrc5" has no OAuth authorization information associated to it..."

I encountered this error when trying to link a requirement from RRC to a work item in RTC. I was able to make the connection to RRC to view and select from the list of available artifacts to attach, however this error message was received when trying to save the work item with the new link.

I checked the rootservices xml and I did not see any invalid web addresses like in the examples above.

Similar issue here. Tested by Work item going from RTC to RQM no OAuth Authorization. All appears to be setup correctly.

Not sure if related, went from federated to LDAP. In a log file it says it is trying to connect with admin ID because we have trusted checked in OAuth.

Unchecked trusted and now it just says invalid login or password.

Ideas?