Firefox is getting rid of their existing non-standard crypto interfaces and is "replacing" them with the WebCrypto standard https://bugzilla.mozilla.org/show_bug.cgi?id=1030963 Old - https://developer.mozilla.org/en-US/docs/JavaScript_crypto WebCrypto - https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html This will break our abillity to do browser based enrollment particularly in the key archival functionality.
As a result, we have decided to either improve on the existing CRMFPopClient or add a new REST based CLI (investigation to follow)
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2.2
Per 10.2.2 Triage meeting of 02/24/2015: 10.2.2
master:
CRMF request can be generated and submitted as follows: http://pki.fedoraproject.org/wiki/User_Certificate
Metadata Update from @cfu: - Issue assigned to edewata - Issue set to the milestone: 10.2.2
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/1637
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.
Login to comment on this ticket.