From 9d07e25422939cd8f255fffdbadeb7671ea1d7ac Mon Sep 17 00:00:00 2001 From: Joseph Dougherty Date: Fri, 8 Oct 2021 09:33:21 -0400 Subject: [PATCH] DOCSP-19009 remove references to mongosh --gssapiHostName from the manual --- ...ongodb-windows-with-kerberos-authentication.yaml | 7 ++----- ...ess-to-mongodb-with-kerberos-authentication.yaml | 13 +++++-------- source/reference/configuration-options.txt | 5 ----- 3 files changed, 7 insertions(+), 18 deletions(-) diff --git a/source/includes/steps-control-access-to-mongodb-windows-with-kerberos-authentication.yaml b/source/includes/steps-control-access-to-mongodb-windows-with-kerberos-authentication.yaml index 25cd399b289..02102d14e96 100644 --- a/source/includes/steps-control-access-to-mongodb-windows-with-kerberos-authentication.yaml +++ b/source/includes/steps-control-access-to-mongodb-windows-with-kerberos-authentication.yaml @@ -111,12 +111,9 @@ action: Kerberos name, ensure that you specify the fully qualified domain name (FQDN) for the ``--host`` option, rather than an IP address or unqualified hostname. - - If you are connecting to a system whose hostname does not - match the Kerberos name, use :option:`--gssapiHostName ` - to specify the Kerberos FQDN that it responds to. - pre: | - Alternatively, you can first connect :binary:`mongo.exe + If you are connecting to a system whose hostname does not + match the Kerberos name, first connect :binary:`mongo.exe ` to the :binary:`~bin.mongod.exe`, and then from the :binary:`mongo.exe ` shell, use the :method:`db.auth()` method to authenticate in the ``$external`` diff --git a/source/includes/steps-control-access-to-mongodb-with-kerberos-authentication.yaml b/source/includes/steps-control-access-to-mongodb-with-kerberos-authentication.yaml index 67c609c3a3f..340be414cb4 100644 --- a/source/includes/steps-control-access-to-mongodb-with-kerberos-authentication.yaml +++ b/source/includes/steps-control-access-to-mongodb-with-kerberos-authentication.yaml @@ -118,15 +118,12 @@ action: Kerberos name, ensure that you specify the fully qualified domain name (FQDN) for the ``--host`` option, rather than an IP address or unqualified hostname. - - If you are connecting to a system whose hostname does not - match the Kerberos name, use :option:`--gssapiHostName ` - to specify the Kerberos FQDN that it responds to. - pre: | - Alternatively, you can first connect :binary:`~bin.mongosh` to the - :binary:`~bin.mongod`, and then from :binary:`~bin.mongosh`, use - the :method:`db.auth()` method to authenticate in the - ``$external`` database. + If you are connecting to a system whose hostname does not + match the Kerberos name, first connect :binary:`~bin.mongosh` + to the :binary:`~bin.mongod`, and then from + :binary:`~bin.mongosh`, use the :method:`db.auth()` method to + authenticate in the ``$external`` database. language: javascript code: | use $external diff --git a/source/reference/configuration-options.txt b/source/reference/configuration-options.txt index f80f8ae8fe8..7ba28273d11 100644 --- a/source/reference/configuration-options.txt +++ b/source/reference/configuration-options.txt @@ -2869,11 +2869,6 @@ Key Management Configuration Options and Kerberos authentication. The SASL hostname overrides the hostname only for the configuration of SASL and Kerberos. - For :binary:`~bin.mongosh` and other MongoDB tools to connect to - the new :setting:`~security.sasl.hostName`, see the - ``gssapiHostName`` option in :binary:`~bin.mongosh` and other - tools. - .. setting:: security.sasl.serviceName