Create a means whereby a running CA, KRA, OCSP, TKS, and/or TPS can have its package name and product version identified.
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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1624097, https://bugzilla.redhat.com/show_bug.cgi?id=1639836 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue assigned to mharmsen
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
commit 769392e4feff761767672cd6e58a7eec483ba259 (HEAD -> master, origin/master, origin/HEAD) Author: John Magne jmagne@redhat.com Date: Mon Oct 22 18:31:20 2018 -0600
dogtagpki Pagure Issue #3071 - Identify version/release of pki-ca, pki-kra, pki-ocsp, pki-tks, and pki-tps remotely.
commit a76550e5b3f63893b74e020addbaf3587ddfd7a1 Author: Matthew Harmsen mharmsen@redhat.com Date: Mon Oct 22 16:25:23 2018 -0600
dogtagpki Pagure Issue #3071 - Identify product version of CA, KRA, OCSP, TKS, and TPS using browser (spec file template)
commit f88365fa4a8e9dd7055bb234dbc6496dcf2ab96f Author: Matthew Harmsen mharmsen@redhat.com Date: Mon Oct 22 16:18:04 2018 -0600
dogtagpki Pagure Issue #3071 - Identify product version of CA, KRA, OCSP, TKS, and TPS using browser
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.13 (was: 10.6)
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/3188
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.