#1673 CA console: A registered profile plugin can be deleted when there is an active profile that use this plugin.
Closed: wontfix 4 years ago by dmoluguw. Opened 9 years ago by aakkiang.

CA console: A registered profile plugin can be deleted when there is an active
profile that use this plugin. This is a regression.

Steps to Reproduce:

1. Login to CA console.
2. Select Certificate Manager -> Certificate Profiles.
3. Select "Certificate profile plugin registration" tab.
4. Register a new plugin. plugin saved successfully.
5. In the "Certificate profile instances management" tab create a new profile.
6. Add a policy to this profile, select the newly created plugin.
7. Restart CA.
8. Enable the new profile from the CA agent page.
9. CA console display the profile as enabled.
10. In the "Certificate profile plugin registration" tab, select the new plugin
and Delete.

Actual results:

Plugin deleted successfully.

Expected results:

Plugin should not be deleted when there is a profile instance exist for that
registered plugin.

Per CS/DS meeting of 11/02/2015: 10.4 - minor

Closed as WONT FIX for RHCS 8.x version of product.

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

8 years ago

pkiconsole is deprecated in PKI 10.6+ and potentially removed in future releases. So, closing this tikcet as WONTFIX

Metadata Update from @dmoluguw:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 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/2232

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.

Log in to comment on this ticket.

Metadata