How to I solve the "Unable to receive attribute values" error I get for an attribute customization?
Hello,
I am using RTC 3.0.1.1 configured with URI https://localhost (this is a test environment) and a self-signed SSL certificate generated on websphere.
I have configured an HTTP Filtered Value Set attribute customization to retrieve values from an XML file that I have stored under the project area's source control.
I have configured the com.ibm.team.workitem.service.internal.connector.AuthenticationService ccm server setting with an account that is used to retrieve the data (the value is "ID|||account|||password") which has been made a Project Administrator for the project area. Within the HTTP Filtered Value Set configuration I am using "Basic Authentication" with the credential identifier set to ID and the username and password blank (I have also tried setting these... it doesn't seem to make a difference)
When I create a work item, instead of providing the values from the XML file I get the error "Unable to receive attribute values (HTTP request failed with 302 Found)". Since I am using a self-signed certificate I flagged the option "Ignore invalid SSL certificates" but I get the error "Unable to receive attribute values (Problems accessing 'XML data source URL': Connection to https://localhost refused)."
I thought that this might be the result of the jre not accepting a self-signed certificate so I extracted it from websphere and imported the .crt into the cacerts keystore belonging to the jre that the application is configured to use. I still get the same error...
When I login to the project are with the credentials specified in the AuthenticationService and access the XML data source URL that is provided in the error, I can download it without any problems, which is why I think it has something to do with the self-signed certificate and the jre.
Any ideas as to what this could be?
Thank you and best regards,
Andrew
|
4 answers
Just use Form based authentication and use
"j_username" for username parameter "j_password" for password parameter. You should also use "https://servername:9443/ccm/j_security_check" for URL and "ID" for Credential Identifier. ID can be changed according to your definition in your ccm/admin->Advanced Properties But you say: "XML file that I have stored under the project area's source control", I dont think RTC might be able to fetch that item. You should call a webservice in the XML DataSource URL like "https://servername:9443/ccm/oslc/contexts/_hAweEADbEeGk55ehjdc7IA/workitems" What did you use in the XML data Source URI? Comments Hello Canberk,
You will not be able to fetch the xml file by that method. You can only fetch the reportable rest api of the Jazz Product if I'm not mistaken.
Andrew, I have seen this use case work before (using SCM as the HTTP Value set provider), although this approach is not officially supported. The XML data source URL you're using looks right, although there is no port (is that on purpose?). I'm not sure this is a cert problem given that you've selected to ignore invalid SSL certs. You should select the same authentication method in your value set definition as your server is set up to use. If it is Basic, you only need to provide a username and password. Can you confirm you also have a row XPath expression defined? Perhaps a screen shot of the value set configuration would help.
|
I am having the same issue. Below is an example of the XML file and configuration.
<Defect>
<Types>
<Type>Enhancement</Type>
</Types>
</Defect>
Row XPath expression: //Defect/TestTypes/TestType
Column XPath expressions: ./
Column identifiers:
Entry label format:
|
@Michael - what error were you seeing? The xpath in your sample doesn't look like it matches the xml. I think it should be //defect/types/type
Comments You are right. Typo on my part. But that's just an example. I had it correct in the system. I still get the red circle with the X next to the field. When I hover over, I get "Unable to receive attribute values (HTTP request failed with 302 Found)" |
|
Based on comments in this workitem:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=174347 the 302 error being seen appears to be due to this defect, fixed in 4.0: https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=181120 What happens if you uncheck the "Ignore invalid SSL certificates" option? I can reproduce the connection refused error by removing the port number from the URL for the XML data source. Of course doing that would also cause the same URL to fail in a browser, which is not what Andrew described. So the original problem remains a bit of a mystery. Perhaps its worth explicitly adding the port to the localhost URL to see what happens. https://localhost:443/ccm/service/com.ibm.team.filesystem.service.internal.rest.IFilesystemContentService/_eQp88UnNEeK3x-eF3YRumA/_eUWKIEnNEeK3x-eF3YRumA/MetaDataCommon.xml?itemId=_lQ0NAEnNEeK3x-eF3YRumA Comments Hello Brian,
I think adding the port is a must. A 302 is better than a connection refused (at least you're getting into the application). After some more digging, I suspect this is the defect you are running into. The HTTPConnector is not following redirects (see comment 1). This was fixed in 4.0 and backported to 3.0.1.3 via 193423
Hello Brian,
|
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.
Comments
Andrew, please have a look at this post from Jorge Diaz: http://jorgediazblog.wordpress.com/2012/06/27/work-item-customization-httpconector-and-oauth-in-rtc-4-0-for-oslc/ it explains your situation well. And as mentioned below, you might not be able to access all the data you want.