Bug 1373178

Summary: Lightweight CA signing cert not revoked upon deletion
Product: Red Hat Enterprise Linux 7 Reporter: Fraser Tweedale <ftweedal>
Component: pki-coreAssignee: RHCS Maintainers <rhcs-maint>
Status: CLOSED ERRATA QA Contact: Asha Akkiangady <aakkiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: akasurde, arubin, edewata, ksiddiqu, lmiksik, mharmsen
Target Milestone: rc   
Target Release: 7.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pki-core-10.3.3-9.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 05:27:19 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:
Attachments:
Description Flags
console.log none

Description Fraser Tweedale 2016-09-05 12:25:00 UTC 
Description of problem:

Lightweight CA signing certificate is not revoked upon deletion.

Version-Release number of selected component (if applicable): 10.3


How reproducible: always


Steps to Reproduce:
1. delete lightweight CA


Actual results:

The deleted CA's signing certificate has not been revoked

Expected results:

The deleted CA's signing certificate is revoked.

Additional info:
Comment 2 Endi Sukma Dewata 2016-09-06 18:56:36 UTC 
Fixed in master (10.4):
* af8ff4a7c36614c1b41338f9e32a83462d4163be
Comment 4 Abhijeet Kasurde 2016-09-16 13:01:47 UTC 
Verified using IPA version::

ipa-server-4.4.0-11.el7.x86_64

Marking BZ as verified.
Comment 5 Abhijeet Kasurde 2016-09-16 13:02:03 UTC 
Created attachment 1201639 [details]
console.log
Comment 7 errata-xmlrpc 2016-11-04 05:27:19 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://rhn.redhat.com/errata/RHBA-2016-2396.html