From e4966f9c3f9566603be24e09f4803b3183898272 Mon Sep 17 00:00:00 2001 From: Rob Crittenden Date: Mon, 17 Feb 2020 15:10:46 -0500 Subject: [PATCH] Don't fully quality the FQDN in ssbrowser.html for Chrome The trailing dot causes it to not function as expected, remove it from the example. https://pagure.io/freeipa/issue/8201 Reviewed-By: Christian Heimes --- install/html/ssbrowser.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/install/html/ssbrowser.html b/install/html/ssbrowser.html index faa7e657b..a48a24511 100644 --- a/install/html/ssbrowser.html +++ b/install/html/ssbrowser.html @@ -105,7 +105,7 @@ Double-click the network.negotiate-auth.trusted-uris entry to display the Enter string value dialog box.
  • - Enter the name of the domain against which you want to authenticate, for example, .example.com. + Enter the name of the domain against which you want to authenticate, for example, .example.com.
  • Return to Web UI
  • @@ -147,13 +147,13 @@
  • Create a new /etc/opt/chrome/policies/managed/mydomain.json file with write privileges limited to the system administrator or root, and include the following line:
    - { "AuthServerWhitelist": "*.example.com." } + { "AuthServerWhitelist": "*.example.com" }
    You can do this by running:
    - [root@server]# echo '{ "AuthServerWhitelist": "*.example.com." }' > /etc/opt/chrome/policies/managed/mydomain.json + [root@server]# echo '{ "AuthServerWhitelist": "*.example.com" }' > /etc/opt/chrome/policies/managed/mydomain.json