Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1624097

Summary: CC: Identify version/release of pki-ca, pki-kra, pki-ocsp, pki-tks, and pki-tps remotely [RHEL]
Product: Red Hat Enterprise Linux 7 Reporter: Matthew Harmsen <mharmsen>
Component: pki-coreAssignee: Jack Magne <jmagne>
Status: CLOSED ERRATA QA Contact: Asha Akkiangady <aakkiang>
Severity: high Docs Contact:
Priority: high    
Version: 7.6CC: cfu, cpelland, dmoluguw, edewata, jmagne, mharmsen, msauton, sumenon
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: pki-core-10.5.16-2.el7 Doc Type: Enhancement
Doc Text:
The following information needs to find its way into the Common Criteria documentation: To identify the product version of a running RHCS server, a theme package must be installed (e. g. - redhat-pki-server-theme). The theme package NVR must be of an identical version as the installed subsystem (pki-ca, pki-kra, pki-ocsp, pki-tks, and/or pki-tps). To identify the exact version of a running CA, KRA, OCSP, TKS, or TPS, utilize something similiar to the following URLs: * http://<pki.example.com>:8080/ca/admin/ca/getStatus * http://<pki.example.com>:8080/kra/admin/kra/getStatus * http://<pki.example.com>:8080/ocsp/admin/ocsp/getStatus * http://<pki.example.com>:8080/tks/admin/tks/getStatus * http://<pki.example.com>:8080/tps/admin/tps/getStatus
Story Points: ---
Clone Of:
: 1639836 1643879 (view as bug list) Environment:
Last Closed: 2019-08-06 13:07:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1639836, 1639837, 1643879, 1718418, 1774181, 1804951, 1823906, 1848778, 1887979, 1895104, 1914474, 1952719, 1960688, 1974464, 2003854, 2003855, 2016512, 2033132, 2079511, 2092152, 2119835, 2136537, 2168017, 2180218, 2183555, 2275961    
Attachments:
Description Flags
Revised fix. mharmsen: review+

Description Matthew Harmsen 2018-08-30 23:42:35 UTC
Common Criteria (CC) certification requires some method whereby all versions of all relevant PKI packages are stored for easy identification.

This bug proposes that a file be used, although these could also be referenced via a pop-up or as part of a banner.

Comment 1 Matthew Harmsen 2018-09-27 19:07:07 UTC
Per PKI Team meeting, re-assigned to mharmsen

Comment 10 Jack Magne 2018-10-19 22:29:18 UTC
Created attachment 1495797 [details]
Revised fix.

Comment 12 Jack Magne 2018-10-19 23:32:12 UTC
Test Procedure:

(1) install all 10.5.9 packages including redhat-pki-server-theme.
(2) Verify that the following file exists:

    % ls /usr/share/pki/CS_SERVER_VERSION
    /usr/share/pki/CS_SERVER_VERSION

    % cat /usr/share/pki/CS_SERVER_VERSION 
    Red Hat Certificate System 9.4

(3) Install a CA using default values
(4) Execute the following URL in a browser:
    
    https://<pki.example.com>:8443/ca/services

(5) Verify that the title reads:

    Red Hat® Certificate System 9.4

(6) Hover the mouse over the shadowman icon in the page; instructions to visit
     www.dogtagpki.org should be displayed

(7) Click on the shadowman icon to verify that the external Dogtag Wiki is
    displayed:

    http://www.dogtagpki.org/wiki/PKI_Main_Page

(8) Test the getStatus page for the CA like follows:

Use a browser and view the info at the following url:

http://<pki.example.com>:8080/ca/admin/ca/getStatus


It should look similar to this:

<XMLResponse>
<State>1</State>
<Type>CA</Type>
<Status>running</Status>
<Version>10.5.9-5.0.el7</Version>
<ProductVersion>Red Hat Certificate System 9.4</ProductVersion>
</XMLResponse>



(9) Install and test the other subsystems as follows:


* http://<pki.example.com>:8080/kra/admin/kra/getStatus
* http://<pki.example.com>:8080/ocsp/admin/ocsp/getStatus
* http://<pki.example.com>:8080/tks/admin/tks/getStatus
* http://<pki.example.com>:8080/tps/admin/tps/getStatus

Comment 15 Sudhir Menon 2019-06-12 11:29:01 UTC
Fix is seen.

[root@pki1 config2]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.7 Beta (Maipo)

pki-ca-10.5.16-2.el7.noarch
pki-tks-10.5.16-2.el7pki.noarch
pki-tps-10.5.16-2.el7pki.x86_64
pki-base-10.5.16-2.el7.noarch
pki-kra-10.5.16-2.el7.noarch
pki-ocsp-10.5.16-2.el7pki.noarch
redhat-pki-server-theme-10.5.16-2.el7pki.noarch

[root@pki1 pki]# pwd
/usr/share/pki
-rw-r--r--.  1 root root   31 Apr 24 21:13 CS_SERVER_VERSION
-rw-r--r--.  1 root root   70 Apr  4 12:50 VERSION

#rpm -qf CS_SERVER_VERSION
redhat-pki-server-theme-10.5.16-2.el7pki.noarch

Observations:

1. Title is displayed as "Red Hat® Certificate System 9.5" in https://pki1.example.com:8443/ca/services
2. Hovering over new logo displays Visit dogtagpki.org for more information about RHCS products and services.
3. Upon clicking the redhat new logo the external Dogtag Wiki is displayed i.e http://www.dogtagpki.org/wiki/PKI_Main_Page
4. getStatus displays the version of each of the subsystem.

http://pki1.example.com:8080/ca/admin/ca/getStatus
<XMLResponse>
<State>1</State>
<Type>CA</Type>
<Status>running</Status>
<Version>10.5.16-2.el7</Version>
<ProductVersion>Red Hat Certificate System 9.5</ProductVersion>
</XMLResponse>

http://pki1.example.com:20080/kra/admin/kra/getStatus
<XMLResponse>
<State>1</State>
<Type>KRA</Type>
<Status>running</Status>
<Version>10.5.16-2.el7</Version>
<ProductVersion>Red Hat Certificate System 9.5</ProductVersion>
</XMLResponse>

http://pki1.example.com:25080/tps/admin/tps/getStatus
<XMLResponse>
<State>1</State>
<Type>TPS</Type>
<Status>running</Status>
<Version>10.5.16-2.el7</Version>
<ProductVersion>Red Hat Certificate System 9.5</ProductVersion>
</XMLResponse>

http://pki1.example.com:23080/tks/admin/tks/getStatus
<XMLResponse>
<State>1</State>
<Type>TKS</Type>
<Status>running</Status>
<Version>10.5.16-2.el7</Version>
<ProductVersion>Red Hat Certificate System 9.5</ProductVersion>
</XMLResponse>

http://pki1.example.com:26080/ocsp/admin/ocsp/getStatus
<XMLResponse>
<State>1</State>
<Type>OCSP</Type>
<Status>running</Status>
<Version>10.5.16-2.el7</Version>
<ProductVersion>Red Hat Certificate System 9.5</ProductVersion>
</XMLResponse>

5. CS_SERVER_VERSION and VERSION files in /usr/share/pki directory displays the required information.
[root@pki1 pki]# cat CS_SERVER_VERSION
Red Hat Certificate System 9.5

[root@pki1 pki]# cat VERSION 
Name: pki
Specification-Version: 10.5
Implementation-Version: 10.5.16

Comment 17 errata-xmlrpc 2019-08-06 13:07:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2228