-
Notifications
You must be signed in to change notification settings - Fork 144
Remove Firefox PKI GUI Configuration Panel Interface #1683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Comment from mharmsen (@mharmsen) at 2014-08-29 00:56:47 Checked in patch for (1), (2), and (3): |
Comment from mharmsen (@mharmsen) at 2014-08-29 00:57:28 Moving to 10.2.1. |
Comment from mharmsen (@mharmsen) at 2014-09-18 03:50:29 Proposed Milestone: 10.2.3 (per CS Meeting of 09/17/2014) |
Comment from mharmsen (@mharmsen) at 2014-09-25 21:42:00 proposed Milestone: 10.2.2 - Per Dogtag 10.2.3 meeting of 09/25/2014 |
Comment from mharmsen (@mharmsen) at 2015-02-24 23:45:32 Per 10.2.2 Triage meeting of 02/24/2015: 10.2.3 |
Comment from mharmsen (@mharmsen) at 2015-04-28 20:40:04 Per Dogtag 10.2.x TRIAGE meeting of 04/28/2015: cleanup (low/minor priority) |
Comment from mharmsen (@mharmsen) at 2015-06-30 20:37:10 Per Dogtag 10.2.6 TRIAGE meeting of 06/30/2015: 10.3 |
Comment from edewata (@edewata) at 2015-10-20 23:53:09 The wizard classes need be removed to help removing legacy HttpClient. See ticket 342. |
Comment from edewata (@edewata) at 2015-10-22 17:38:35 Removed unused WizardServlet in master: 60fa66a Remaining tasks:
Once ticket 1107 is fixed, we can remove base/server/share/webapps/pki/admin and also dependencies on Velocity. |
Comment from mharmsen (@mharmsen) at 2017-02-27 14:11:46 Metadata Update from @mharmsen:
|
This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue will be closed for inactivity. If the problem is still present reopen this or create a new issue. |
This issue was migrated from Pagure Issue #1120. Originally filed by mharmsen (@mharmsen) on 2014-08-23 00:22:45:
Dogtag 10.2 currently provides the following PKI instance installation/configuration mechanisms:
When the 'pkispawn' utility configures a PKI instance, it utilizes the REST interface; however, the GUI browser interface utilizes the original non-REST legacy interface. Both methods eventually utilize the same configuration back-end.
To alleviate many of the design/development/testing/support problems associated with maintaining multiple interfaces, we are planning on removing the GUI browser configuration interface option in Dogtag 10.2 since:
Completion of this ticket requires the following:
The text was updated successfully, but these errors were encountered: