dogtagpki

#2235 Obsolete cert chain format in PKI 10.2.x
Closed: Invalid Opened by edewata.

Closed: Invalid
Reopen Issue

The code to import existing CA certificate (ticket #456) depends on the new certificate chain format with BEGIN/END PKCS7 added in ticket #1699. Since ticket #456 was backported to 10.2.x, the installation code only accepts the new format. However, the CA still generates the old format with BEGIN/END CERTIFICATE CHAIN. For consistency (and to avoid regression), the #1699 should be backported to 10.2.x as well.

Downstream, this change has already been addressed in:

  • https://fedorahosted.org/pki/ticket/1699#comment:11 (10.2.5 - RHEL 7.2)
  • https://fedorahosted.org/pki/ticket/1699#comment:14 (10.2.6 - RHCS 9)

It has since been released:

This ticket only applies to the following upstream 10.2.x branches:

  • DOGTAG_10_2_6_BRANCH (10.2.6 for Fedora 22 and Fedora 23)
  • DOGTAG 10.2_BRANCH (10.2.x master)

Fixed in 10.3.

Metadata Update from @edewata:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.2.x

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

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
None
None
None
Normal
defect
Installation/Configuration
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.