#1398 Provide UI Javascript warning for missing Mozilla Crypto Object in the CA
Closed: Fixed Opened by jmagne.

The CA's UI has in the past relied upon a Mozilla crypto object to perform key generation and key archival tasks in our certificate enrollment UI.

Now that Mozilla has removed this crypto object with no replacement, the user is now greeted with puzzling errors when enrolling for certificates. One such example is when someone tried to apply for a dual use ECC cert. The result of this was a new ticket complaining about ECC support.

Although we are aware of the root cause of the problem, the users will not be.

The purpose of this ticket is to write a but of javascript that runs when the user first logs into the CA's UI. This javascript will detect for the absence of the crypto object. If said absence is confirmed, we should pop up a helpful Javascript warning box telling the user about the problem and tell them a brief list of operations that will not work.

This should hopefully aid in turning off the stream of related tickets.


Per CS/DS meeting of 06/08/2015: 10.2.6

commit bd780990a15d10c3df9a8da81486878012e00884
Author: Jack Magne jmagne@localhost.localdomain
Date: Tue Jun 16 10:09:01 2015 -0700

Mozilla crypto object warning:
Provide simple textual warning when the user is using a browser that no longer supports the crypto object, which results in reduced CA certficat enrollment functionality. For simplicity provide the warning at the top of the main index page and at the top of the CA's services page. The services page is where the pkispawn of the CA points the uers after installation. The ticket originally called for a JS warnign but the simple text warning should be less intrusive and repetitive to the user.
Ticket #1398 Provide UI Javascript warning for missing Mozilla Crypto Object in the CA.

Very simple change verbally acked by Endi:

Pushed to master.

Closing:

Metadata Update from @jmagne:
- Issue set to the milestone: 10.2.5

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

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