Troubleshooting: IWA Not Working on Chrome or Chromium Edge

Version Affected: All
 
 

Overview

Despite WindowsSSO/IWA being enabled, Chrome and Edge prompt for credentials or throw a 401 error.

Cause

The browser's own settings aren't allowing Kerberos to be used against the IdP URL.

Resolution:

On the end user's workstation:

1. Open Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge for Edge, or HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome for Chrome -- create the key if it doesn't already exist.
2. Add a string value named AuthNegotiateDelegateAllowlist, with the IdP URL as its value (an exact URL or a wildcard such as *.secureauthlab.com).
3. Repeat for a string value named AuthServerAllowlist, with the same value.

Special Considerations

These registry value names are case-sensitive. ADMX files are available from the browser vendors to set them via Group Policy instead.


 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.