Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

MacOS Catalina - setting security.enterprise_roots.enabled to true - Doesn't work as expected

  • 1 antwoord
  • 1 heeft dit probleem
  • 17 weergaven
  • Laatste antwoord van Mike Kaply

Firefoxer
Firefoxer
more options

When a user, on a MacOS Catalina, sets the security.enterprise_roots.enabled to true in Firefox, the certificates are not read from MacOS keychain store.

The method used to set the parameter to true:

Use Firefox on MacOS Catalina, type 'about:config' in the address bar. If prompted, accept any warnings. Right-click to create a new boolean value, and enter 'security.enterprise_roots.enabled' as the Name Set the value to 'true'

What is your recommendation to bypass this problem without manually importing the certificates in the FF certificates authorities ? The goal is to read the certificates from the system store. This parameter works perfectly on MacOS Mojave & Windows.

When a user, on a MacOS Catalina, sets the security.enterprise_roots.enabled to true in Firefox, the certificates are not read from MacOS keychain store. The method used to set the parameter to true: Use Firefox on MacOS Catalina, type 'about:config' in the address bar. If prompted, accept any warnings. Right-click to create a new boolean value, and enter 'security.enterprise_roots.enabled' as the Name Set the value to 'true' What is your recommendation to bypass this problem without manually importing the certificates in the FF certificates authorities ? The goal is to read the certificates from the system store. This parameter works perfectly on MacOS Mojave & Windows.

Alle antwoorden (1)

Mike Kaply
Mike Kaply
  • Top 25 Contributor
  • Moderator
more options

We've tested this and have not encountered this problem.

Could you open a bug in bugzilla and we can work with the certificate team to diagnose the problem?