
#FIREFOX DARK THEME FIX ABOUT CONFIG WINDOWS#
You should note that when a browser is added to the list of Supported user agents, if the client does not authenticate using Windows Integrated Authentication it will not fall back to Forms-Based authentication, but to Basic as per ADFS 2.0. You should add the current list of Supported User Agents to a custom variable and then append the Mozilla/5.0 agent string to ensure that no other functionality will be broken. Set-ADFSProperties -WIASupportedUserAgents “MSIE 6.0”, “MSIE 7.0”, “MSIE 8.0”, “MSIE 9.0”, “MSIE 10.0”, “Trident/7.0”, “MSIPC”, “Windows Rights Management Client”, “Mozilla/5.0”) An example of the command used for adding the required User Agent String is as follow: Set-ADFSProperties | Select WIASupportedUserAgentsĬurrent versions of Chrome and Firefox (at time of writing) can be enabled by adding Mozilla/5.0 to the Supported User Agent Strings.


To check the currently supported User Agent Strings you should run the following command: NB – This functionality is also available in ADFS 2.0, although it was not officially supported by Microsoft. To enable this functionality you can add additional supported User Agent Strings to the ADFS configuration. The supported User Agent Strings for ADFS 3.0 by default do not support Single Sign-On from Third-Party browsers, i.e.
