#2921 CMC: Revocation works with an unknown revRequest.issuer
Closed: fixed Opened by mharmsen.

Originally certificate is signed by user which has issuer "revRequest.issuer=UID=usercert,CN=usercert". Now i wanted to revoke cert.

I did change in revoke config and add "revRequest.issuer=UID=usercert,CN=usercert1" which is incorrect and doesn't match with expected.

With this , revocation works. Should it match the issuer with the one who originally issues cert (as mentioned in ldap)??

See associated bug for Steps to Reproduce.


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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1541526
- Custom field type adjusted to None
- Custom field version adjusted to None

Up for reviw: https://review.gerrithub.io/398312

commit c2c5bdad088fabbb89a8d3634530c74dae78c875 (HEAD -> master, origin/master, origin/HEAD)
Author: Christina Fu cfu@redhat.com
Date: Sat Feb 3 15:50:24 2018 -0800

Ticket #2921 CMC: Revocation works with an unknown revRequest.issuer
This patche adds check between the issuer value of the RevokeRequest against the issuer of the certificate to be revoked.
fixes: https://pagure.io/dogtagpki/issue/2921
Change-Id: Ib2bb2debeb7d1c7ffea1799b5c32630062ddca6a

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.5.5 (was: 10.5)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.5-1.fc27

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/3039

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata