We have observed a corner case when performing a pkidestroy on a TPS instance under the following conditions:
1. Everything is hooked up to one of our supported hsms 2. The machine is in FIPS mode
One of the final steps of the pkidestroying of a TPS instance is to attempt to clean up any TPS connectors that re registered within the TKS. This is because the TPS needs to keep in constant contact with the TKS during it's normal operations.
When a TPS is removed, the TKS should have that connection information de-registered or removed from the TKS's CS.cfg. This is mainly a cleanup issue.
In our described scenario, what happens is the SSL client auth http message that is sent from the pkidestroy script and the TKS fails in the SSL handshake.
Additional info:
Additional information in associated bug pkidestroy of KRA shows similar issue.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1545902 - Custom field type adjusted to None - Custom field version adjusted to None
Per 10.5.x/10.6 Triage: 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
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/3061
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.