Request ability to generate CA signing certificate PKCS10 requests that include the subject key identifier (SKI) in them.
Some considerations:
Include a pkispawn configuration option that will include the SKI in the CA signing certificate request.
After the CA is built, include a method to generate a new CA signing certificate request, using the same key pair, and include the SKI in the request; maybe something using the pki command or some other Dogtag commands.
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=1491453 - Custom field type adjusted to None - Custom field version adjusted to None - Issue assigned to ftweedal - Issue priority set to: critical - Issue set to the milestone: 10.5
Per PKI Team Meeting of 20180118 moving to 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Required NSS changes have landed upstream. See https://bugzilla.mozilla.org/show_bug.cgi?id=430198 for details. Hopefully it will not be too much longer and we can finally fix this in Dogtag.
PR for Dogtag 10.6: https://github.com/dogtagpki/pki/pull/114
Pushed to master:
master
Closing this now, although backport to dogtag 10.5 may be non-trivial.
Metadata Update from @ftweedal: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2974
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.