The "Windows NT" fragment is sent by desktop operation system. The command above will ensure that AD FS only covers the following use cases for WIA: User Agents
#Windows nt 6.2 download windows
If you have AD FS on Windows Server 2016 or later: Set-AdfsProperties -WIASupportedUserAgents 6.0", "MSIE 7.0 Windows NT", "MSIE 8.0", "MSIE 9.0", "MSIE 10.0 Windows NT 6", "Windows NT 6.3 Trident/7.0", "Windows NT 6.3 Win64 圆4 Trident/7.0", "Windows NT 6.3 WOW64 Trident/7.0", "Windows NT 6.2 Trident/7.0", "Windows NT 6.2 Win64 圆4 Trident/7.0", "Windows NT 6.2 WOW64 Trident/7.0", "Windows NT 6.1 Trident/7.0", "Windows NT 6.1 Win64 圆4 Trident/7.0", "Windows NT 6.1 WOW64 Trident/7.0","Windows NT 10.0 WOW64 Trident/7.0", "MSIPC", "Windows Rights Management Client", "=~Windows\s*NT.*Edg.*") If you have AD FS on Windows Server 2012 R2 or earlier: Set-AdfsProperties -WIASupportedUserAgents 6.0", "MSIE 7.0 Windows NT", "MSIE 8.0", "MSIE 9.0", "MSIE 10.0 Windows NT 6", "Windows NT 6.3 Trident/7.0", "Windows NT 6.3 Win64 圆4 Trident/7.0", "Windows NT 6.3 WOW64 Trident/7.0", "Windows NT 6.2 Trident/7.0", "Windows NT 6.2 Win64 圆4 Trident/7.0", "Windows NT 6.2 WOW64 Trident/7.0", "Windows NT 6.1 Trident/7.0", "Windows NT 6.1 Win64 圆4 Trident/7.0", "Windows NT 6.1 WOW64 Trident/7.0","Windows NT 10.0 WOW64 Trident/7.0","MSIPC", "Windows Rights Management Client", "Edg/","Edge/") The following Windows PowerShell example provides the best guidance for the current set of devices that are on the market today that support seamless WIA: Particularly, Windows devices have similar user agent strings with minor variations in the tokens. However, these may be out of date based on changes to browsers and devices. You can view the current settings using the following PowerShell example: Get-AdfsProperties | select -ExpandProperty WiaSupportedUserAgentsīy default, a new AD FS installation has a set of user agent string matches created. AD FS analyzes the user agent string when performing logins in a browser or browser control. The WIASupportedUserAgents defines the user agents which support WIA. The above means you no longer have to configure individual user agent strings to support common Edge scenarios, even though they are updated quite often.įor other browsers, configure the AD FS property WiaSupportedUserAgents to add the required values based on the browsers you are using.
By default, Windows Integrated Authentication (WIA) is enabled in Active Directory Federation Services (AD FS) in Windows Server 2012 R2 for authentication requests that occur within the organization's internal network (intranet) for any application that uses a browser for its authentication.ĪD FS 2016 now has an improved default setting that enables the Edge browser to do WIA while not also (incorrectly) catching Windows Phone as well: =~Windows\s*NT.*Edg.*
0 kommentar(er)
