We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

FF 62.0.2 ADMX & Certificates

  • 2 réponses
  • 5 ont ce problème
  • 10 vues
  • Dernière réponse par 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?

Toutes les réponses (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 Auteur de la question
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.