#1397 Subsystem deregistration cleanup
Closed: migrated 3 years ago by dmoluguw. Opened 8 years ago by edewata.

Currently the subsystem deregistration is implemented as a deployment scriptlet which is executed on the client side by pkidestroy:

# remove kra connector from CA if this is a KRA
deployer.kra_connector.deregister()

# remove tps connector from TKS if this is a TPS
deployer.tps_connector.deregister()

deployer.security_domain.deregister(None)

This means the scriptlet needs to handle the implementation detail of each subsystem and make sure that the same code will work with all subsystems.

The code can be simplified by moving the code to the server so each subsystem can execute a custom code to deregister itself without having to deal with other subsystems. The pkidestroy scriptlet should simply call a generic method:

deployer.config_client.deregister()

Proposed milestone: 10.3


Per CS/DS meeting of 06/08/2015: 10.3

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

7 years ago

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/1958

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata