Bug 2132047

Summary:	Check hidden status for PKINIT certificate creation
Product:	Red Hat Enterprise Linux 8	Reporter:	Aleksandr Sharov <asharov>
Component:	ipa	Assignee:	Florence Blanc-Renaud <frenaud>
Status:	CLOSED MIGRATED	QA Contact:	ipa-qe <ipa-qe>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	8.6	CC:	rcritten, tscherf
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 20:41:14 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:

Description Aleksandr Sharov 2022-10-04 13:57:23 UTC

Description of problem:
ipa-pkinit-manage disable > remove kdc cert > ipa-pkinit-manage enable solution doesn't work correctly for hidden replica, because IPA doesn't consider replica status for this process, and hidden replica isn't a public KDC.

Version-Release number of selected component (if applicable):
ipa-server-common-4.9.8-7.module+el8.6.0+14337+19b76db2.noarch
certmonger-0.79.13-5.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install replica
2. Make it hidden with # ipa server-state $HOSTNAME --state=hidden
3. Try to renew cert, either with certmonger resumbission or ipa-pkinit-manage disable > remove kdc cert > pkinit enable 

Actual results: 
You end up with self-signed certificate even for replica with CA. 

Expected results:
Either get an informative error (proposing using ipa server-state $HOSTNAME --state=active to do the same) or request the cert from other PKIs

Additional info:

Comment 3 RHEL Program Management 2023-09-18 20:36:11 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-18 20:41:14 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.