Enable Integrated Windows Authentication (IWA) | Google ChromeIssue Users are presented with a prompt to enter the credentials instead of using the active SAML session established through WIndows login. Configuration: Authentication context for SAML2.0 configured to use Windows-based authentication. From Multi-Provider SSO > Identity Providers.On SAML2 Update1 IdP recordThe AuthnContextClassRef method that we will be included in our SAML 2.0 AuthnRequest to the Identity Provider is set to urn:federation:authentication:windows. Reference: https://docs.servicenow.com/csh?topicname=t_SupportKerberosAuthentication.html&version=latest Expected result: With Kerberos, a SAML session is already active through an established Windows login, so the user does not need to authenticate with the IdP. Behavior observed: The user is been prompted to enter the credentials from the IDP on the google chrome Browser.ReleaseAll releases.CauseIntegrated Authentication with Kerberos requires that the browser being used to access the site be configured to retrieve the currently logged in user from the client machine.ResolutionChrome reads a key from the registry on the windows system, AuthNegotiateDelegateWhitelist. This key configures Chrome to allow certain sites to use Kerberos (and to allow delegation). The key can be implemented in two ways: As a policy in a Group Policy ObjectAdded manually in the registry on the client machine where Chrome is installed. To make the change via group policy please check with your windows administrator and he would be in a position to set up a group policy to update the key accordingly. Please follow the below steps to add the key manually. Close any open instances of Chrome.From run open regedit.Go to the path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\ChromeAdd a new String value named AuthNegotiateDelegateWhitelist.On the value data add the hostname which you would like to be whitelisted. This change does not require the machine to be restarted to take effect. However, please close any instance of chrome which is opened up before making this change. More details about this