dogtagpki

#3169 upgrade: add SANToCNDefault to registry
Closed: fixed by edewata. Opened by ftweedal.

Closed: fixed
Reopen Issue

From discussion in https://github.com/dogtagpki/pki/pull/354 :

Question, why not add the upgrade script in PKI? This change is made in PKI so there will be a discrepancy between new PKI instances and old ones without an upgrade script.

FYI, I'm considering to add CLIs to manage the registry properties so it's easier to update them.

Metadata Update from @edewata:
- Issue assigned to edewata

https://github.com/dogtagpki/pki/pull/363

Metadata Update from @edewata:
- 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

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

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

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
None
None
None
None
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.