When a CA instance is created with an external CA, the certs issued by this new CA instance issues certs with CertificateIssuerName encoded with its own choosing instead of using the exact CertificateSubjectName encoding that was given by the external CA.
This causes certificate validation issue.
commit 5bbd06e6e77729c63d65b77445f71f63ea0cdd1f Author: Christina Fu cfu@redhat.com Date: Wed Oct 15 10:30:31 2014 -0700
Bug1151147 issuerDN encoding correction
patch checked into DOGTAG_10_1_BRANCH as well.
Per CS/DS meeting of 10/27/2014: Milestone - 10.2.1
pushed to DOGTAG_10_2_0_BRANCH
commit 1984b5af6f3632110d91fc0f4a36a929335ec086 Author: Christina Fu cfu@redhat.com Date: Wed Oct 15 10:30:31 2014 -0700
... To ssh://git.fedorahosted.org/git/pki.git 7fbe698..1984b5a DOGTAG_10_2_0_BRANCH -> DOGTAG_10_2_0_BRANCH
Metadata Update from @cfu: - Issue assigned to cfu - Issue set to the milestone: 10.2.1
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/1752
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.