In case of a user-signed CMC requests, they must be through HTTPS and the SSL client auth cert must match that of the CMC signing cert.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1460764 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical
Metadata Update from @mharmsen: - Issue assigned to cfu
commit 63c9582009b3858a6878863b9658d04c9aad45c1 Author: Christina Fu cfu@redhat.com Date: Wed Jun 14 14:57:10 2017 -0700
Metadata Update from @cfu: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.8 (was: 10.4)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.1-10.el7
Metadata Update from @mharmsen: - Custom field fixedinversion reset (from pki-core-10.4.1-10.el7)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.9 (was: 10.4.8)
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/2857
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.