Bug 1608781

Summary:	certmonger not generating thumbprints while requesting a CA-signed Certificate Through SCEP.
Product:	Red Hat Enterprise Linux 7	Reporter:	Gaurav Swami <gswami>
Component:	certmonger	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED ERRATA	QA Contact:	ipa-qe <ipa-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.5	CC:	nalin, ndehadra, pvoborni, rcritten, sumenon
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	certmonger-0.78.4-12.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1789934 (view as bug list)		Environment:
Last Closed:	2020-03-31 19:44:23 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:	1789934

Comment 2 Rob Crittenden 2018-07-26 19:14:57 UTC

The issue is likely that certmonger always includes &message=<id> with its requests and it does a GetCACaps and GetCACert request when setting up a CA. The default id is 0 which matches what is seen here.

The CA expects this to be a valid CA id which it isn't so it blows up.

certmonger should not be including message when it does not have a valid ca ident.

Comment 3 Rob Crittenden 2018-07-26 21:47:58 UTC

Fixed in upstream

master:

https://pagure.io/certmonger/c/60a4db5796b0575ca2cc9f1af4ecb3fdc6359242

Comment 9 Sudhir Menon 2019-12-11 14:27:06 UTC

Marking the bug as VERIFIED using

pki-server-10.5.17-6.el7.noarch
pki-ca-10.5.17-6.el7.noarch
ipa-server-4.6.6-11.el7.x86_64

[11/Dec/2019:02:30:35 -0500] "GET /ca/cgi-bin/pkiclient.exe?operation=GetCACert HTTP/1.1" 200 969
[11/Dec/2019:02:30:35 -0500] "GET /ca/cgi-bin/pkiclient.exe?operation=GetCACert&message=1 HTTP/1.1" 200 969

Comment 11 errata-xmlrpc 2020-03-31 19:44:23 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-2020:1052