Issues With Intel® EMA Server Authentication Due to NTLM Deprecation in Browsers

• Microsoft* announced the phased deprecation of NTLM authentication on Windows* and Windows servers* as of June 2024.
• This deprecation does not impact EMA server configuration directly.
• Issues may arise with EMA server authentication as browsers stop supporting NTLM.
• The problem is likely related to browser settings rather than EMA server configuration. 

1. Check Browser Configuration:

   • Ensure that the browser is configured to use Kerberos authentication instead of NTLM.

2. For Firefox:

   • Open Firefox and type about:config in the address bar.
   • Set network.negotiate-auth.trusted-uris to .vprodemo.com to enable Firefox to use the logged-in Windows account without NTLM.
   • Additionally, set network.auth.private-browsing-sso to true to allow Firefox private (incognito) mode to use the logged-in Windows account.

     Note	This setting will prevent the use of a different account.

3. For Chrome:

   • Open the Windows* registry editor on the computer where Chrome is running.
   • Set AuthServerAllowlist and AuthNegotiateDelegateAllowlist to *.vprodemo.com to enable Chrome to use the logged-in Windows* account without NTLM.
   • Additionally, set AmbientAuthenticationInPrivateModesEnabled to 1 to allow Chrome incognito mode to use the logged-in Windows account.

     Note	This setting will prevent the use of a different account.

   • Alternatively, use Group Policy to configure these settings for multiple computers.

For detailed steps on configuring Kerberos authentication in different browsers, refer to the article: https://woshub.com/enable-kerberos-authentication-in-browser/