Versions Compared

Old Version 13

changes.mady.by.user Steinar Line

Saved on

compared with

New Version Current

changes.mady.by.user Steinar Line

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To check whether your Chrome uses the AuthServerAllowlist, take a look at URL: chrome://policy 

If Chrome policies state " No policies set, " Chrome on Windows will instead use Local Intranet Zone. Your site must be added to that list for Chrome to work with Kerberos on Windows. Chrome on other operating systems requires policies to work with Kerberos.

Info

When defined, Chrome policies override the Windows Local Intranet Zone List.
Refer to https://www.chromium.org/developers/design-documents/http-authentication  and https://www.chromium.org/administrators/policy-list-3#HTTPAuthentication  for details.

Expand
titleOS X

On OS X you may run commands below with your domain names in a terminal window to configure Chrome. Restart Chrome afterward. The first command removes the deprecated name AuthServerWhitelistthat was replaced by AuthServerAllowlistin 2020:
defaults delete com.google.Chrome AuthServerWhitelist
defaults write com.google.Chrome AuthServerAllowlist ".example.com,.otherexample.com"

Policies that may affect how Chrome and Kerberos works:

  • AuthSchemes: Specifies which HTTP authentication schemes are supported by Google Chrome. Possible values are 'basic', 'digest', 'ntlm' and 'negotiate'. Kerberos requires 'negotiate.' If this policy is left unset, all four schemes will be available.     

  • AuthServerAllowlist: Specifies which servers should be whitelisted for integrated authentication. Integrated authentication is only enabled when Google Chrome receives an authentication challenge from a proxy or from a server that is in this permitted list, e.g., *.example.com or serversjira.example.com,confluence.example.com must be added. Separate multiple server names with commas. When unset,  Chrome will try to detect if a server is on the Intranet, and only then will it respond to IWA requests. IWA requests from non-intranet servers will be ignored by Chrome. 

Image Modified
Expand
titleTesting your setup in Kantega SSO

When you believe you have configured the correct group policy to have Kerberos working and also have followed guide to set up Kerberos support in Kantega SSO, please navigate to Kerberos test page verify all is set up correctly. You will on the Kerberos test page get help on what may be remaining to have your setup work:

Image Modified

Using short-form URLs

Info

Note that when accessing the application using the short format URL (http://issues), browsers will still look for an SPN in the FQDN format (issues.example.com) 

...