dogtagpki

#1112 Add a GUI browser option to import an Admin Certificate (for compatibility with the REST interface)
Closed: Invalid Opened by mharmsen.

Closed: Invalid
Reopen Issue

The current GUI browser configuration was not designed to account for the Dogtag 10 instances which can now contain more than one PKI subsystem. Therefore, if the GUI browser configuration mode is utilized, it will always generate an admin certificate for that subsystem.

This is problematic when attempting to utilize a common Firefox profile, since the singular PKI instance now contains two separate and distinct admin certificates.

The REST configuration interface addresses this problem by providing an option for a subsystem to import and utilize an existing admin certificate rather than creating a new one.

This option needs to be added to the GUI panels to make them compatible with the REST interface.

proposed Milestone: 10.3

This is being resolved as 'wontfix' since we have decided to remove the GUI browser configuration panels interface.

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.2 - 08/14 (August)

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

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
None
None
None
None
Normal
defect
Installation/Configuration
Installer Cleanup/ Improvement
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.