Kerberos Authentication fails with Google Chrome even though Internet Explorer works fine.
search cancel

Kerberos Authentication fails with Google Chrome even though Internet Explorer works fine.

book

Article ID: 136669

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) SITEMINDER

Issue/Introduction

Kerberos Authentication Scheme is configured and the Integrated Windows Authentication works properly with the Internet Explorer. (Windows Desktop login to Web Single Sign-On works seamlessly.)

Tried the same thing with Google Chrome but the Web access was rejected with the message "Server Error. The server was unable to process your request."

Environment

Release : 12.8

Component : SITEMINDER SECURE PROXY SERVER

Resolution

Web server (Access Gateway) hostname needs to be added to the Windows registry "AuthNegotiateDelegateWhitelist" for Kerberos authentication with Google Chrome on Windows.


Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome

        Name: AuthNegotiateDelegateWhitelist

        Type: REG_SZ

       Value: <FQDN of the Web server (Access Gateway)>


Additional Information

https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthNegotiateDelegateWhitelist