Bug 2132047 - Check hidden status for PKINIT certificate creation
Summary: Check hidden status for PKINIT certificate creation
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.6
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Florence Blanc-Renaud
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-04 13:57 UTC by Aleksandr Sharov
Modified: 2023-07-31 06:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-10200 0 None None None 2023-07-31 06:56:16 UTC
Red Hat Issue Tracker RHELPLAN-163861 0 None None None 2023-07-31 06:57:41 UTC

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:
Note You need to log in before you can comment on or make changes to this bug.