Bug 1370519 - Certificate revocation in service-del and host-del isn't aware of Sub CAs
Summary: Certificate revocation in service-del and host-del isn't aware of Sub CAs
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
Depends On:
TreeView+ depends on / blocked
Reported: 2016-08-26 14:31 UTC by Petr Vobornik
Modified: 2016-11-04 06:02 UTC (History)
7 users (show)

Fixed In Version: ipa-4.4.0-10.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-11-04 06:02:22 UTC
Target Upstream Version:

Attachments (Terms of Use)
console.log (6.37 KB, text/plain)
2016-09-12 04:49 UTC, Abhijeet Kasurde
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Petr Vobornik 2016-08-26 14:31:37 UTC
This bug is created as a clone of upstream ticket:

As a part of the procedure of deleting a service or host entry, any certificates issued for them are revoked.

The function that revokes the certificate (located in service plugin module) is not aware of Sub CAs and calls cert-show without cacn option. This causes a fail because the cert-show will assume the `ipa` CA for a certificate signed by a Sub CA.

This causes an error during certificate revocation that aborts the delete operation.

Comment 3 Fraser Tweedale 2016-09-05 16:41:42 UTC
Current behaviour: service-del and host-del commands fail with error
if the service or host has been issued a cert from a sub-CA.

Therefore, this is important to fix.

Comment 5 Jan Cholasta 2016-09-07 06:14:42 UTC
Upstream ticket:

Comment 11 Abhijeet Kasurde 2016-09-12 04:49:04 UTC
Verified using IPA version::

Marking BZ as verified.

Comment 12 Abhijeet Kasurde 2016-09-12 04:49:30 UTC
Created attachment 1200068 [details]

Comment 14 errata-xmlrpc 2016-11-04 06:02:22 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.


Note You need to log in before you can comment on or make changes to this bug.