Currently most deployment parameters are used with slot variables:

• The default value needs to be specified in the default.cfg:

pki_master_crl_enable=True

• A slot variable needs to be defined in pkislots.cfg:

MASTER_CRL_ENABLE_SLOT=[MASTER_CRL_ENABLE]

• The slot variable gets assigned in pkiparser.py:

self.mdict['MASTER_CRL_ENABLE_SLOT'] = self.mdict['pki_master_crl_enable']

• Then the parameter can finally be used (e.g. in CS.cfg):

ca.crl.MasterCRL.enable=[MASTER_CRL_ENABLE]

To troubleshoot a problem with a deployment parameter, first we'd have to search the deployment parameter itself, then find the slot variable, then search where the slot variable is used.

The current code actually already supports using deployment parameters without slot variables.

• The default value still needs to be specified in the default.cfg:

pki_master_crl_enable=True

• Then the parameter can be used directly (e.g. in CS.cfg):

ca.crl.MasterCRL.enable=[pki_master_crl_enable]

With this mechanism we can search where the deployment parameter is used directly.

Proposed change: To simplify troubleshooting the existing slot variables should be removed and replaced with direct parameter substitutions.