Currently to add a new TPS connector the user will have to add the properties manually as documented in pki-tps-connector man page. The UI should provide a wizard where the user can select the type of connector to create (e.g. CA/TKS/KRA), then enter the parameters required by the connector (e.g. hostname, port), then the wizard will generate the properties based on the parameters.
This is a follow-up of ticket #890.
cfu wrote:
also, please note that the configuration for failover (search for the word "Failover" in the CS.cfg for config tips) is slightly different. If you want, you can make the wizard (and ui) smarter in allowing people to configure that properly.
Per CS/DS meeting of 5/5/2014, moving to milestone 10.2 Backlog.
Christina requests this earlier rather than later; consequently, this ticket is being marked "critical".
Proposed Milestone: 10.3 (per CS Meeting of 09/17/2014)
We will need to build base classes for UI wizard and panels first, then we can build the wizard for TPS connectors. The base classes can be used for creating other wizards.
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: UNTRIAGED
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/1555
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.