Hello Patrick,Thank you for your response. This is a very strange issue and I really don't think it is a web browser config/compatibility issue with Chrome or FireFox. Let me give you a bit more background for your assessment:Chrome and FireFox browsers currently works with IWA but only if the apps are pointing to the current/old IWA auth scheme which is a combination of IIS webagent r12.0 SP3 on Windows Server 2008. We build a new Windows Server 2016 and installed SiteMinder IIS webagent r12.52 SP1 CR09 and configured IIS website for IWA authentication. Now when we point our internal intranet web apps to the new IWA auth scheme, then it appears to only work with IE but not with Chrome or FF.The agenttrace.log file on the new IWA server shows that the user was authenticated by the policy server and identified the user as well as creating the SMSESSION cookie and then pass the browser back to the application TARGET, but it appears that the SMSESSION cookie would only exist on the IE browser but not on Chrome or FF and therefore the webagent on the application web server will redirect the request back to the IWA server to obtain SMSESSION cookie and hence, goes into a loop.The fact that IWA works on both Chrome and FF if the browser is redirected to the old/current IWA auth scheme, but not on the new IWA auth scheme, this would make me think that both Chrome and FF browsers are configured to work with Windows Authentication. Also when these browsers hit the new IWA auth scheme, the agenttrace.log file showed that it authenticated the user and created the SMSESSION cookie which proves that the browsers successfully passed the user's identity to the IWA server.If you have any additional insights I would love the help.Thanks!