Closed pki-bot closed 4 years ago
Comment from mharmsen (@mharmsen) at 2017-11-22 14:45:46
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2018-01-18 16:54:37
Per PKI Team Meeting of 20180118 moving to 10.6
Comment from mharmsen (@mharmsen) at 2018-01-18 16:54:38
Metadata Update from @mharmsen:
Comment from ftweedal (@frasertweedale) at 2018-05-24 20:18:01
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.
Comment from ftweedal (@frasertweedale) at 2018-12-06 08:37:45
PR for Dogtag 10.6: https://github.com/dogtagpki/pki/pull/114
Comment from ftweedal (@frasertweedale) at 2018-12-17 01:04:01
Pushed to master
:
Comment from ftweedal (@frasertweedale) at 2018-12-18 04:10:51
Closing this now, although backport to dogtag 10.5 may be non-trivial.
Comment from ftweedal (@frasertweedale) at 2018-12-18 04:10:51
Metadata Update from @frasertweedale:
This issue was migrated from Pagure Issue #2854. Originally filed by mharmsen (@mharmsen) on 2017-11-22 14:45:02:
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.