After updating to 2020-5.0, users are prompted for credentials when using AD FS in CCH Axcess™
- Article Type:
- Problem Resolution
- Last Modified:
- 11/05/2022
Symptoms
After updating to 2020-5.0, users are prompted for credentials when using AD FS in CCH Axcess™
Environment
Microsoft AD FS
Cause
Edge (Chromium) is not listed as a WIA supported user agent
Resolution
- Open a PowerShell window on the AD FS Server as administrator. Search for Power Shell, right click and select Run as Administrator.
- Enter: Get-AdfsProperties | select -ExpandProperty WiaSupportedUserAgents
- Be sure to keep record of all currently enabled Agents as they will need to be included in the next command
- Once we have the list, we can add Edge(Chromium) as a supported browser using command: Set-AdfsProperties -WIASupportedUserAgents @( )
- For Server 2012 and Prior: Edg/ and Edge/
- For Server 2016 and later: =~Windows\s*NT.Edg.
- Enter: Get-AdfsProperties | select -ExpandProperty WiaSupportedUserAgents and ensure that the original agents are listed in addition to what was added
*PLEASE REMEMBER TO INCLUDE ALL THE AGENTS LISTED IN STEP 2*
2012 Example:
Set-AdfsProperties -WIASupportedUserAgents @("MSIE 6.0", "MSIE 7.0; Windows NT", "MSIE 8.0", "MSIE 9.0", "MSIE 10.0; Windows NT 6", "MSIPC", "Windows Rights Management Client", "Edg/","Edge/")
2016 Example:
Set-AdfsProperties -WIASupportedUserAgents @("MSIE 6.0", "MSIE 7.0; Windows NT", "MSIE 8.0", "MSIE 9.0", "MSIE 10.0; Windows NT 6", "MSIPC", "Windows Rights Management Client", "=~Windows\s*NT.*Edg.*")
Below is a link to a Microsoft article that goes through this process in-depth and provides the naming conventions of WIA supported agents:
https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/configure-ad-fs-browser-wia
Additional Information
N/A
Solution Id | 000157756/000135820 |
---|---|
Direct Link |