dogtagpki

#952 Simplifying configuration resource creation in TPS UI
Closed: migrated by dmoluguw. Opened by edewata.

Closed: migrated
Reopen Issue

Previously to create a new TPS configuration resource (e.g. profile, connection) the user needs to duplicate existing resource properties in the CS.cfg and fix the property names manually. Currently in the UI users can create a new resource and add the properties with the proper names one-by-one. Later in the UI the user will be able to copy the existing properties into a new resource in bulk (ticket #936), but the user will still need to fix the property names manually. All of these methods are time consuming.

Option #1: The UI can provide a mechanism to clone an existing resource and rename the properties automatically.

Option #2: The UI can provide a list of templates from which a new resource can be created. This way the TPS does not need to be prepopulated with unused resources.

Proposed milestone: May

This is a generic ticket for all TPS configuration. New tickets tickets may need to be created for specific TPS resources. The TPS connector configuration is already covered in #989.

Metadata Update from @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/1518

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)
Metadata
None
None
None
None
Normal
defect
TPS
10 days
TPS Rewrite
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.