#2912 Automatic range adjustment for CAValidityDefault.
Closed: migrated 3 years ago by dmoluguw. Opened 6 years ago by edewata.

In ticket #2389 the ValidityDefault was modified to support automatic range adjustment. The caCACert profile uses ValidityDefault, so it is working fine.

However, the caCMCcaCert profile is using CAValidityDefault which currently does not support automatic range adjustment. So subordinate CA installation with CMC may fail unless the caCMCcaCert profile is manually modified to use a smaller range.

Per discussion with cfu, it should be fixed as follows:

  • The CAValidityDefault should be modified to support installAdjustValidity parameter just like in ValidityDefault, but it will default to true.
  • Modify caCACert profile to use CAValidityDefault as well so it will be consistent with caCMCcaCert profile.

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 type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

6 years ago

The error message should be improved as well:

Number of controls is 1
Control #0: CMCStatusInfoV2
   OID: {1 3 6 1 5 5 7 7 25}
   BodyList: 0
   Status String: Request Not After Invalid Rejected - {1}
   OtherInfo type: FAIL
     failInfo=internal ca error
ERROR: CMC status for [0]: failed

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

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.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata