This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

FF 62.0.2 ADMX & Certificates

  • 2 respostas
  • 5 have this problem
  • 10 views
  • Last reply by RDP-MIB

RDP-MIB
RDP-MIB
more options

I've just started to test the ADMX files that are now available as of FF62 and ESR60, we are running the general release and not the ESR. In the past we had imported our certs into the CERT8.DB file using a VB Script during login.

I see that via the ADMX that there is now a variety of support options, including importing Root Certificates - but it does not seem to be working.

I try a URL in IE and it works fine, same URL in FF gives me a certificate warning.

Thoughts?

I've just started to test the ADMX files that are now available as of FF62 and ESR60, we are running the general release and not the ESR. In the past we had imported our certs into the CERT8.DB file using a VB Script during login. I see that via the ADMX that there is now a variety of support options, including importing Root Certificates - but it does not seem to be working. I try a URL in IE and it works fine, same URL in FF gives me a certificate warning. Thoughts?

All Replies (2)

worzie
worzie
more options

Evidently this does not include intermediate certs. You must have them added to the cert store via GPO as well.

RDP-MIB
RDP-MIB Question owner
more options

Worzie - we already import the certs that we issue from our CA into the cert store, I'm not having this issue in IE.

Guess I'll keep running the VB Script for the time being until the import can be corrected, I'll look posting this on the Git-Hub bugs list.