Bug 1373178 - Lightweight CA signing cert not revoked upon deletion
Summary: Lightweight CA signing cert not revoked upon deletion
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.3
Assignee: RHCS Maintainers
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-05 12:25 UTC by Fraser Tweedale
Modified: 2016-11-04 05:27 UTC (History)
6 users (show)

Fixed In Version: pki-core-10.3.3-9.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 05:27:19 UTC
Target Upstream Version:

Attachments (Terms of Use)
console.log (4.48 KB, text/plain)
2016-09-16 13:02 UTC, Abhijeet Kasurde 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2396 0 normal SHIPPED_LIVE pki-core bug fix and enhancement update 2016-11-03 13:55:03 UTC

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