DOCSP-1834: scram part2

Author: kay-kim

source/core/authentication-mechanisms.txt

@@ -33,7 +33,7 @@ Default Authentication Mechanism
 .. versionchanged:: 3.0
 
 As of MongoDB 3.0, :ref:`Salted Challenge Response Authentication
-Mechanism (SCRAM) <authentication-scram-sha-1>` is the default
+Mechanism (SCRAM) <authentication-scram>` is the default
 authentication mechanism for MongoDB.
 
 Previous versions used :doc:`MONGODB-CR </core/security-mongodb-cr>` as

source/core/security-mongodb-cr.txt

@@ -27,6 +27,6 @@ identify the user.
 
 MongoDB no longer defaults to ``MONGODB-CR`` and instead uses
 :ref:`Salted Challenge Response Authentication Mechanism (SCRAM)
-<authentication-scram-sha-1>` as the default authentication mechanism.
+<authentication-scram>` as the default authentication mechanism.
 
 .. include:: /includes/fact-mongodb-cr-users.rst

source/tutorial/configure-fips.txt

@@ -69,7 +69,7 @@ system. However, if your environment requires FIPS compliant encryption
 uses only FIPS-compliant encryption.
 
 MongoDB's FIPS support covers the way that MongoDB uses OpenSSL for
-network encryption, ``SCRAM-SHA-1`` authentication, and x.509
+network encryption, SCRAM authentication, and x.509
 authentication. If you use Kerberos or LDAP authentication, you must
 ensure that these external mechanisms are FIPS-compliant.
 ``MONGODB-CR`` authentication is **not** FIPS compliant.

source/tutorial/control-access-to-mongodb-windows-with-kerberos-authentication.txt

@@ -93,7 +93,7 @@ Incorporate Additional Authentication Mechanisms
 
 Kerberos authentication (:ref:`GSSAPI <security-auth-kerberos>` (Kerberos))
 can work alongside MongoDB's challenge/response authentication mechanisms
-(:ref:`SCRAM-SHA-1 <authentication-scram-sha-1>` and
+(:ref:`SCRAM-SHA-1 <authentication-scram>` and
 :ref:`MONGODB-CR <authentication-mongodb-cr>`), MongoDB's
 authentication mechanism for LDAP (:ref:`PLAIN <security-auth-ldap>`
 (LDAP SASL)), and MongoDB's authentication mechanism for x.509 (

source/tutorial/control-access-to-mongodb-with-kerberos-authentication.txt

@@ -168,7 +168,7 @@ Incorporate Additional Authentication Mechanisms
 
 Kerberos authentication (:ref:`GSSAPI <security-auth-kerberos>` (Kerberos))
 can work alongside MongoDB's challenge/response authentication mechanisms
-(:ref:`SCRAM-SHA-1 <authentication-scram-sha-1>` and
+(:ref:`SCRAM-SHA-1 <authentication-scram>` and
 :ref:`MONGODB-CR <authentication-mongodb-cr>`), MongoDB's
 authentication mechanism for LDAP (:ref:`PLAIN <security-auth-ldap>`
 (LDAP SASL)), and MongoDB's authentication mechanism for x.509 (

source/tutorial/enforce-keyfile-access-control-in-existing-replica-set-without-downtime.txt

@@ -31,8 +31,8 @@ enforcing authentication.
    enforcing authentication in an existing MongoDB 3.2 replica set.
 
 This tutorial uses the :ref:`keyfile <internal-auth-keyfile>` internal
-authentication mechanism for internal security, and :ref:`SCRAM-SHA-1
-<authentication-scram-sha-1>`-based :ref:`role-based access controls
+authentication mechanism for internal security, and
+:ref:`authentication-scram`-based :ref:`role-based access controls
 <authorization>` for client connections.
 
 Cloud Manager and Ops Manager

source/tutorial/enforce-keyfile-access-control-in-existing-sharded-cluster-no-downtime.txt

@@ -57,9 +57,9 @@ IP Binding
 Internal and Client Authentication Mechanisms
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-This tutorial configures authentication using :ref:`SCRAM-SHA-1
-<authentication-scram-sha-1>` for client authentication and a :ref:`keyfile
-<internal-auth-keyfile>` for internal authentication.
+This tutorial configures authentication using
+:ref:`authentication-scram` for client authentication and a
+:ref:`keyfile <internal-auth-keyfile>` for internal authentication.
 
 Refer to the :ref:`authentication` documentation for a complete list of
 available client and internal authentication mechanisms.