![]() Too late in the night to experiment any further. On macOS, paths are based on the Contents/Resources directory of the Firefox.app. If I remove that URL key, again none of the pages load. On Windows, paths are based on directory where Firefox is installed. If I manually create the registry entry 'URL' containing a website URL '\HKEYLOCALMACHINE\SOFTWARE\Policies\Mozilla\Firefox\Homepage' then reopen Firefox, not only does the manually entered URL appear but so do all the additional pages I have set through the OMA-URI policy. It seems, Firefox is maybe keeping a cache of some precompiled JavaScript and does not use my changed file? Or it is not enough to sabotage the Registry-Access and Firefox picks up another configuration? Setting up AutoConfig To use AutoConfig, you need to create two files, one at the top level, and one in a subdirectory. Only so far, I could not stop it from reading the Registry. I verified, Firefox does not start if the omni.ja is missing and on the other hand, it will actually start with my modification. I tried changing it and wrapped the extracted folder back in a zip archive using the "store-only" compression. Use of versions prior to TLS 1.2 are not permitted. SSL 2.0 and SSL 3.0 contain a number of security flaws. ![]() These versions must be disabled in compliance with the Network Infrastructure and Secure. The installed version of Firefox must be supported. The file is found again as "extracted-omni/components/EnterprisePolicies.js Using versions of an application that are not supported by the vendor is not permitted. The very same file is contained in your Firefox installation in a file called "omni.ja" which is actually a zip-archive, that can be extracted. The file browser/components/enterprisepolicies/EnterprisePolicies.js was changed Google Chrome Internet Explorer version 9.0 and higher Mozilla Firefox. ![]() The Windows SSO setting itself can be found in Firefox under Settings, Privacy & Security, Logins and Passwords.According to this Anti-Feature was added back in Firefox 60. So letâs get started! Collect the required policy setting information In this article, I only show how to configure the Windows SSO setting. In that article, I explained configuring Firefox with Intune in more depth, like how to ingest the ADMX file. ![]() If youâre not familiar yet with configuring Mozilla Firefox using Microsoft Intune, I suggest to first read this article. Add a batch file to do that on each system startup, and you're all set. Just change the value of FirefoxHomepage to fix the problem. When we use the ADMX file which supports Firefox 91 or later, we can configure this setting using Microsoft Intune, as I showed in previous blog posts for other settings. This was the registry key which was doing that for my Firefox: HKEYUSERS\\Software\Policies\Firefox.To provide our users a better sign-in experience when using Firefox, let us admins configure the settings for them. This provides the end-user a single sign-on (SSO) experience on a (Azure AD joined) Windows device when the user signs in to Office 365 and other Azure AD-connected resources like we already have when using Microsoft Edge. ![]() Since the release of Mozilla Firefox 91, we have the option to configure Windows single sign-on for Microsoft work and school accounts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |