+1 on proposed priority/milestone

Per discussions in PKI Bug Council of 01/19/2017 it was determined that this bug would not be addressed until 10.4.

Checked into master:

049a4e3e09328bfcdff62dc189ad95917647fb22

New parameters to pkispawn are:

pki_ca_signing_record_create=True
pki_ca_signing_serial_number=1

I the migration case, these must be set to:

pki_ca_signing_record_create=False
pki_ca_signing_serial_number=X

where X is the serial number of the signing cert being imported (in decimal)

The signing cert record will be delted at the end of the install, so that it can be imported from the old migration data. All fields in the old migration data will then be correct.

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

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.