The latest Firefox no longer supports CRMF key generation, so a client certificate has to be requested via CLI (see http://pki.fedoraproject.org/wiki/User_Certificate), exported into PKCS #12, then imported manually into Firefox via its configuration panel.
To simplify the process, the CLI could provide a command to export directly into Firefox, thus eliminating the manual import process, for example:
$ pki -c <client database password> client-cert-export <nickname> \ --firefox [--firefox-profile <profile name>]
By default the profile name will be "default".
Per CS/DS Meeting of 6/1/2015: 10.3
This can be implemented with the following steps.
First, parse the Firefox profile configuration file at ~/.mozilla/firefox/profiles.ini. It contains the following entries:
[General] StartWithLastProfile=0 [Profile0] Name=default IsRelative=1 Path=4kwhz8ay.default ...
Get the "Path" of the profile that is going to be used. In this case the "default" profile will have a path of "4kwhz8ay.default".
Use the path to construct the NSS database path: ~/.mozilla/firefox/4kwhz8ay.default.
Finally, perform the certificate import operation using the above NSS database path.
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/1956
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)