dogtagpki

#1113 kra connector deletion does not work in pkidestroy
Closed: Fixed Opened by vakwetu.

Closed: Fixed
Reopen Issue

There are a few things wrong:

  1. On pkidestroy, we have code to remove the kra connector from the ca on which it was configured. But the ca can be cloned and therefore have entries in other ca's. We should really remove it from all clones. As a short term solution, we should examine the security domain and eliminate it on all clones.

Failure to do so leads to a failure to reinstall, starting with a clone because an entry exists with another ca host:port and a different transport cert.

The long term solution is probably to put connector information in LDAP, so that an update can easily be propagated to all clones, keeping in mind the failover semantics of the config.

  1. when run from pkidestroy (using sslget), removing a kra connector fails due to media type not being provided. (ie. returns 415)

Attempted this with masters and clones in IPA.

To ssh://vakwetu@git.fedorahosted.org/git/pki.git
99e6330..0507afc master -> master

Metadata Update from @vakwetu:
- Issue assigned to vakwetu
- Issue set to the milestone: 10.2 - 08/14 (August)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1676

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
Normal
defect
Auth
IPA
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.