#8201 update ssbrowser.html
Closed: fixed by rcritten. Opened by thelvaen.

Issue

Chrome (at least in version 80) does not understand the trailing dot in the json file for Kerberos auth.

Steps to Reproduce

  1. Configure Kerberos authentication in /etc/opt/chrome/policies/managed/domain.json with a trailing dot on the domain, for example:
    { "AuthServerWhitelist": ".example.com.", "AuthNegotiateDelegateWhitelist": ".example.com." }
  2. Try login with Kerberos/Chrome on your IPA instance,

Actual behavior

Chrome does not autolog using the Kerberos ticket

Expected behavior

Chrome should autolog to IPA using Kerberos ticket

Version/Release/Distribution

ipa-server-4.6.5-11.el7.centos.4.x86_64
ipa-client-4.6.5-11.el7.centos.4.x86_64
389-ds-base-1.3.9.1-12.el7_7.x86_64
pki-ca-10.5.16-6.el7_7.noarch
krb5-server-1.15.1-37.el7_7.2.x86_64

Additional info:

doc file ipa/config/ssbrowser.html should not give ".example.com." but ".example.com" instead


Metadata Update from @rcritten:
- Issue assigned to rcritten

https://github.com/freeipa/freeipa/pull/4252

Metadata Update from @rcritten:
- Issue priority set to: normal
- Issue set to the milestone: FreeIPA 4.8.5

master:

  • e4966f9c3f9566603be24e09f4803b3183898272 Don't fully quality the FQDN in ssbrowser.html for Chrome

ipa-4-8:

  • f356d5734662d0a20f06702353b2f10f29b9f55d Don't fully quality the FQDN in ssbrowser.html for Chrome

Metadata Update from @rcritten:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

master:

  • 9eb1be875276c61127663c3860228f03a66ebfbd Part2: Don't fully quality the FQDN in ssbrowser.html for Chrome

ipa-4-8:

  • 8a5bfaba83da700bed29fc82ef1d280bfabb8379 Part2: Don't fully quality the FQDN in ssbrowser.html for Chrome
Metadata