In ticket #448 (possibly PKI 10.1) the default DN encoding was changed from PrintableString to UTF8String. Certificates issued before the change will have subject DN encoded in PrintableString. If the server is upgraded and the certificate is renewed, the new certificate will have subject DN encoded in UTF8String. This could become a problem especially on CA certificates since certificate verification would fail if the encoding does not match.
The certificate renewal code needs to be fixed to reuse the same subject DN encoding used in the original certificate regardless of the current encoding configuration.
Until this is fixed, upgraded server might have to be configured to use the old encoding (at least for CA renewal) with this parameter in CS.cfg:
X500Name.directoryStringEncodingOrder=PrintableString,UTF8String,T61String,BMPString,UniversalString
Metadata Update from @edewata: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' (was: FUTURE) - Custom field proposedpriority adjusted to '' (was: critical) - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue priority set to: 2 - Issue set to the milestone: FUTURE (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: FUTURE)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Metadata Update from @ftweedal: - Issue assigned to ftweedal
Per 10.5.x/10.6 Triage: 10.5.x
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.6)
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/2707
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)
Login to comment on this ticket.