Firefox for Enterprise Support Forum

Hello

We use our own CA to secure some websites on the internal network. Until version 101.0, the SSL was working correctly. I have updated today to firefox 101 and all our internal websites started giving SSL_ERROR_BAD_CERT_DOMAIN. There are no issues with external CA issued certificates, so I'm assuming it is something related to the way we generate the certificates. Were there any changes done at version 101 which might reject certificates with a valid common name? Is there a way to disable it and revert to version 100 options?

Thank you

Every time Firefox is opened it gives an error message (see image).

I have tried:

• Deleting and reinstalling.
• Deleting Firefox folder in //users/xxxxxxx/Library/Application Support & //Library/Caches then uninstalling Firefox.
• Both above using older Firefox versions.

This issue is happening on all of the Macs in our org. We have no custom configurations. The pkg is installed via FileWave device management. It occurs whether installed through FileWave or manually.

Thanks

Dear Madam or Sir,

there seem to be new performance settings to be available since Firefox 91: https://support.mozilla.org/en-US/kb/performance-settings

While I have been able to "Use hardware acceleration when available" by using ...

{

 "policies": {
   "HardwareAcceleration": false
 }

}

... I could not find any setting to disable "Use recommended performance settings". Is there any possible way to disable this feature in dsitribution/policies.json ?

Thank you very much in advance!

Best regards

Victor

We have an intranet portal that we have been running for years that is based on .net 2.0 IIS application pool. We push firefox preferences out and a few things I think that make this work are these network.automatic-ntlm-auth.allow-non-fqdn = true network.automatic-ntlm-auth.trusted-uris = domain.com (our domain name) network.negotiate-auth.trusted-uris = domain.com (our domain name) network.automatic-ntl:m-auth.trusted-uris = .domain.com (our domain name).

Normally our original site proceeded wtihout any issue.

The new site that the vendor wants to upgrade us to has a ton of upgraded code and a slightly updated look and feel and new controls for publishing and configuring content. Like the previous portal, this also runs on IIS but uses .net 4.5 application pool. What happens is when we hit this site in Firefox we are bombarded with a username and password prompt. If you cancel a bunch of times the site will load but eventually it pops up again. If you enter your domain username and password then it goes away and you can use the site normally. IE, Chrome and Edge just go directly to the site, automatically using your current windows login identity so if you post content on the intranet portal it shows as you.

We did a remote session with the vendor of the portal and the guy basically said yeah it has something to do with this .net framework and firefox. We know it worked on the older verison but we've never been able to get it to work in firefox. You'll have to use another browser or enter your domain credentials when you visit the site in firefox.

Does anyone know if there is some sort of under the hood tweak in firefox to get the NTLM passthrough to an IIS based .net 4.5 application like it does with .net 2.0? We would love to keep Firefox as our default browser but when we go live with this portal we may have to switch to Chrome.

Hello,

We have some trouble with Firefox in Windows Roaming Profiles: "The bookmarks and history system will not be functional". The sqlite-shm and sqlite-wal are shown but they are fully inaccessible from CSC (client offline cache). Why does Firefox need to store this temp files in %appdata%? That's really bad design! sqlite-shm and sqlite-wal should be located in %localappdata%.

My solution is to just copy the profile folder, ignoring the inaccessible files. Then I just need to rename it to the original folder name and ff starts just fine. Does anyone know anything more to this problem? Thank you