Description of problem: When ca.scep.enable is set to 'true', the default SCEP configuration currently rejects PKCSReq PKIOperation requests which use MD5 or DES, but the server doesn't respond to GetCACaps requests, so clients have no way of reliably determining what they should be doing instead.
Version-Release number of selected component (if applicable): pki-common-9.0.3-38.el6_6.noarch
How reproducible: Always
Steps to Reproduce: 1. Enable SCEP. 2. curl -v -v -v 'http://$server:9180/ca/cgi-bin/pkiclient.exe?operation=GetCACaps&message=0'
Actual results: 404 error
Expected results: 200 OK, contents based on the ca.scep.allowedEncryptionAlgorithms and ca.scep.allowedHashAlgorithms settings.
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1198257
Metadata Update from @cipherboy: - 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1198257 - Custom field type adjusted to None - Custom field version adjusted to None
Duplicate of https://pagure.io/dogtagpki/issue/627 and https://pagure.io/dogtagpki/issue/1298
Metadata Update from @cipherboy: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
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/3281
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.