When renewing the CA cert via Certmonger, if the CA Subject DN uses PrintableString attribute encoding, the renewed cert will have UTF8String attribute encoding. This causes a variety of problems in other programs because it may regard the new certificate as a different CA.
PrintableString
UTF8String
The problem arises due the the certmonger dogtag-ipa-renew-agent helper uses the following procedure to renew the CA certificate:
dogtag-ipa-renew-agent
profileSubmit
profileReview
profileProcess
The stringified subject DN is included in the profileReview response and re-submitted in the profileProcess request data. Then the string is converted back into a X500Name (this time using the default attribute encoding i.e. UTF8String) and set into the request, potentially changing the attribute encoding from the CSR.
X500Name
https://review.gerrithub.io/#/c/381438/
Metadata Update from @edewata: - 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
Metadata Update from @mharmsen: - Issue assigned to mharmsen
Metadata Update from @mharmsen: - Assignee reset
Metadata Update from @mharmsen: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Fix pushed to master (87b4d00cea01c00f6c0422934fc15b9e06afb6f6)
Metadata Update from @ftweedal: - Issue assigned to ftweedal
Metadata Update from @ftweedal: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.0 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.0-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/2948
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.