Make starting CRL Number configurable

[pki-bot]

This issue was migrated from Pagure Issue #2406. Originally filed by dsirrine (@dsirrine) on 2016-07-20 19:05:04:

• Closed as Fixed
• Assigned to jmagne (@jmagne)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1358439

---

For migration purposes, crlId should be configurable to not conflict with existing CRL's.

Two potential options for implementation could be:

1. pkispawn switch --starting-crl-id
2. CS.cfg configuration option
3. Combination of both
4. default.cfg variable which is able to be overridden

[pki-bot]

Comment from jmagne (@jmagne) at 2016-07-27 23:21:49

Checking in fix:

commit 0c502a3
Author: Jack Magne jmagne@dhcp-16-206.sjc.redhat.com
Date: Wed Jul 27 11:43:33 2016 -0700

Make starting CRL Number configurable.

Ticket 2406 Make starting CRL Number configurable

This simple patch provides a pkispawn config param that passes
some starting crl number value to the config process.

Here is a sample:

[CA]
pki_ca_starting_crl_number=4000

After the CA comes up the value of "crlNumber" in the db will
reflect that value of 4000.

Currently no other values are changed. We can talk about if we
need more values reset in the given case.

Also, this creates a setting in the CS.cfg

ca.crl.MasterCrl.startingCrlNumber=4000

This setting is only consulted when the crl Issuing Point record is created
for the first time.

Closing ticket

[pki-bot]

Comment from edewata (@edewata) at 2016-07-28 21:10:13

This is documented in this page:
http://pki.fedoraproject.org/wiki/CRL_Migration

[pki-bot]

Comment from dsirrine (@dsirrine) at 2017-02-27 14:04:36

Metadata Update from @dsirrine:

• Issue assigned to jmagne
• Issue set to the milestone: 10.3.5