TPS UI: Seeing an error message when trying to edit a general config parameter from the UI using curl command
How reproducible:
always
Steps to Reproduce:
1. curl -E "TPS1_adminV:Secret123" -H "Content-Type: application/xml" --dump-header /tmp/header1 -X PATCH --data @/tmp/input_data -k "https://sigma.lab.eng.rdu.redhat.com:30042/tps/rest/config" 2.TPS1_adminV is a TPS admin cert
Actual results:
The parameter is modified successfully but the above curl command returns and error message; Could not find MessageBodyWriter for response object of type: com.netscape.certsrv.tps.config.ConfigData of media type: application/octet-stream Also seeing the following in /tmp/header1 HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Cache-Control: private Expires: Wed, 31 Dec 1969 19:00:00 EST Set-Cookie: JSESSIONID=3542F5C38C1D0FE6AEE0BE7079287C02; Path=/tps/; Secure; HttpOnly Content-Type: text/html Content-Length: 144 Date: Mon, 23 Feb 2015 15:06:43 GMT Connection: close
Expected results:
The parameter should be updated successfully. The curl command should return the update XML of TPS general config. The header should have HTTP 200 message.
Per 10.2.3 Triage meeting of 02/26/2015: 10.2.3
Moving to 10.2.4 per CS team meeting.
Per Dogtag 10.2.x TRIAGE meeting of 04/28/2015: (Tech Preview Feature)
Per CS/DS meeting of 06/08/2015: 10.2.6
Per Dogtag 10.2.6 TRIAGE meeting of 06/30/2015: 10.3
The client should specify the correct type. Need to provide a better error message and provide an example in the wiki page.
The problem was caused by incorrect default response type. Fixed in master:
Metadata Update from @mharmsen: - Issue assigned to edewata - Issue set to the milestone: 10.3.3
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1838
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.