RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/6257

Per discussion in #6220, add ca-enable and ca-disable commands.

The behaviour already exists in Dogtag; only needs to be exposed via IPA.

Note that ca-del must be updated to handle the case of target CA already
being disabled.

Currently, admins have no way to wholesale disable a CA, i.e. to
prevent it issuing new certificates with the possibility of
re-enabling it at a later time, and ensuring that certificates issued
by the CA can still be managed by FreeIPA.

There is currently no way to do this.  A similar but limited
outcome can be achieved by removing the CA from all CA ACLs but this
has a variable - possibly very high - administrative overhead.

master:
* c7e0dbc4e174d0bb7577de18cdb2f414f4199c57 Add ca-disable and ca-enable commands
ipa-4-4:
* b037e54e457d731cd16144df7573f4c85d79368a Add ca-disable and ca-enable commands

Verified using IPA and PKI version ::

ipa-server-4.5.0-14.el7.x86_64
pki-server-10.4.1-7.el7.noarch

Marking BZ as verified. See attachment for console log.

Created attachment 1283632 [details]
console.log

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://access.redhat.com/errata/RHBA-2017:2304