#1226 Hard-coded range unit in certificate profiles
Closed: Fixed None Opened 9 years ago by edewata.

Currently the 'range' property in certificate profiles only supports a fixed number of days. This limitation makes it difficult to specify common ranges such as years or months due to the varying number of days in those ranges. It also makes it difficult to test certificate expiration since the minimum range is one day.

To address these problems a new optional 'rangeUnit' property should be added. The default value should be 'day'. Other values may include 'second', 'minute', 'hour', 'week', 'month', and 'year'. The actual range (in milliseconds) should be calculated using the Calendar API (http://docs.oracle.com/javase/7/docs/api/java/util/Calendar.html).

Once the 'rangeUnit' is added, the current default of '720 days' in some profiles probably can be replaced with '2 years' to get the proper 2-year range (same starting and ending date).

Proposed milestone: 10.2.x (needed to test #1093)


master: 5d82ad42001875e28a48ba374d4a467c9ec91f5c

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.2.1

7 years ago

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

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.

Login to comment on this ticket.

Metadata