illegalhex opened this Issue on Oct 10, 2017
t seems on the 10.3.X branch of code the endpoint /ca/rest/certrequests/{id} will return a 500 error. On the 10.2.x branch, tested on Fedora 23, this call would return the correct response of the cert request with the corresponding id. The error on 10.3.x was observed on Fedora 24,25, and 26 by following the process outlined on http://pki.fedoraproject.org/wiki/Quick_Start.
Is there something missing in the documentation that is needed to make the api call functional like a specific version of a java library and/or tomcat that isn't specified in the dogtag-pki deb?
Link to the http error and the tomcat error output: https://gist.github.com/illegalhex/3e5497d18518e58a9c1ecdd49acd0d74
edewata added a commit that referenced this issue on Oct 25, 2017
Consolidated PKCS #7 header and footer for Java.
The duplicate PKCS #7 header and footer literals for Java have been consolidated into the PKCS7 class.
https://pagure.io/dogtagpki/issue/2790
Change-Id: I50dab5ab9b3a05cd9ff3de9feae20fd4459badd3
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
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/3023
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.