DOCSP-21665: add CSFLE ref anchors and substitute for doc roles (#881)

* DOCSP-21665: add CSFLE ref anchors and subustitute for doc roles

* build

* build

* build

* fix anchor

* close ref

* build

* build

Author: Chris Cho

source/core/security-automatic-client-side-encryption.txt

@@ -103,7 +103,7 @@ Server-Side Field Level Encryption Enforcement
 ----------------------------------------------
 
 Starting in MongoDB 4.2, the server supports using
-:doc:`schema validation </core/schema-validation>` to enforce encryption
+:ref:`schema validation <schema-validation-overview>` to enforce encryption
 of specific fields in a collection. Clients performing
 :ref:`automatic client-side field level
 encryption <field-level-encryption-json-schema>` have specific behavior
@@ -138,4 +138,4 @@ encryption enforcement, see
 
    /reference/security-client-side-automatic-json-schema.txt
    /reference/security-client-side-query-aggregation-support.txt
-   /reference/security-client-side-encryption-appendix.txt
+   /reference/security-client-side-encryption-appendix.txt

source/core/security-client-side-encryption-key-management.txt

@@ -1,3 +1,5 @@
+.. _manual-manage-cmk-and-dek:
+
 =============================================
 Master Key and Data Encryption Key Management
 =============================================
@@ -20,8 +22,7 @@ Supported Key Management Services
 Client-side field level encryption requires a Key Management Service
 (KMS) for accessing a Customer Master Key (CMK). MongoDB automatically
 encrypts data encryption keys using the specified CMK during 
-:doc:`data encryption key creation 
-</reference/method/KeyVault.createKey>`. 
+:ref:`data encryption key creation <keyvault-createkey-method>`.
 
 Deleting the CMK renders all data encryption keys encrypted with that
 CMK as permanently unreadable, which in turn renders all values
@@ -97,7 +98,7 @@ Key must have at least one policy with the following actions:
       }
 
 For complete documentation on data encryption key management using AWS
-KMS, see :doc:`/tutorial/manage-client-side-encryption-data-keys` and
+KMS, see :ref:`Manage Data Encryption Keys <manual-manage-dek>` and
 select the "Amazon Web Services KMS" tab.
 
 .. _field-level-encryption-azure-keyvault:
@@ -137,7 +138,7 @@ ability to perform the following actions:
 
 For complete documentation on data encryption key management using
 Azure Key Vault, see
-:doc:`/tutorial/manage-client-side-encryption-data-keys` and select the
+:ref:`Manage Data Encryption Keys <manual-manage-dek>` and select the
 "Azure Key Vault" tab.
 
 .. _field-level-encryption-gcp-kms:
@@ -174,7 +175,7 @@ or can be included in a
 
 For complete documentation on data encryption key management using
 Google Cloud KMS, see
-:doc:`/tutorial/manage-client-side-encryption-data-keys` and select the
+:ref:`Manage Data Encryption Keys <manual-manage-dek>` and select the
 "Google Cloud KMS" tab.
 
 .. _field-level-encryption-local-kms:
@@ -188,7 +189,7 @@ be a 96-byte long string.
 
 For complete documentation on data encryption key management using a
 locally managed key, see
-:doc:`/tutorial/manage-client-side-encryption-data-keys` and select the
+:ref:`Manage Data Encryption Keys <manual-manage-dek>` and select the
 "Local Keyfile" tab.
 
 .. _field-level-encryption-keyvault:
@@ -273,10 +274,10 @@ index does not exist, applications *must* create it prior to performing
 data encryption key management.
 
 For complete documentation on data encryption key management, see
-:doc:`/tutorial/manage-client-side-encryption-data-keys`.
+:ref:`Manage Data Encryption Keys <manual-manage-dek>`.
 
 .. toctree::
    :titlesonly:
    :hidden:
 
-   /tutorial/manage-client-side-encryption-data-keys.txt
+   /tutorial/manage-client-side-encryption-data-keys.txt

source/core/security-client-side-encryption.txt

@@ -1,3 +1,5 @@
+.. _manual-csfle-feature:
+
 ==================================
 Client-Side Field Level Encryption
 ==================================
@@ -111,7 +113,7 @@ Explicit (manual) encryption of fields
   per-operation basis.
 
   For more information, see
-  :doc:`/core/security-explicit-client-side-encryption`.
+  :ref:`Explicit (Manual) Client-Side Field Level Encryption <field-level-encryption-explicit>`.
 
 Automatic encryption of fields
   .. include:: /includes/extracts/csfle-enterprise-atlas-only.rst
@@ -132,7 +134,7 @@ Automatic encryption of fields
   on automatic encryption rules.
 
   For more information, see
-  :doc:`/core/security-automatic-client-side-encryption`.
+  :ref:`Automatic Client-Side Field Level Encryption <field-level-encryption-automatic>`.
 
 MongoDB 4.2+ compatible drivers, :binary:`~bin.mongosh`, and the MongoDB
 4.2 or later legacy :binary:`~bin.mongo` shell automatically decrypt
@@ -309,7 +311,7 @@ Enforce Field Level Encryption Schema
 -------------------------------------
 
 Starting with MongoDB 4.2, the server supports using
-:doc:`schema validation </core/schema-validation>` to enforce encryption
+:ref:`schema validation <schema-validation-overview>` to enforce encryption
 of specific fields in a collection. Use the
 :ref:`automatic encryption rule keywords
 <field-level-encryption-json-schema>` with the

source/core/security-explicit-client-side-encryption.txt

@@ -1,3 +1,5 @@
+.. _field-level-encryption-explicit:
+
 ====================================================
 Explicit (Manual) Client-Side Field Level Encryption
 ====================================================
@@ -121,8 +123,9 @@ encryption:
 Server-Side Field Level Encryption Enforcement
 ----------------------------------------------
 
-The MongoDB 4.2 server supports using :doc:`schema validation
-</core/schema-validation>` to enforce encryption of specific fields in a
+The MongoDB 4.2 server supports using 
+:ref:`schema validation <schema-validation-overview>`
+to enforce encryption of specific fields in a
 collection. If the collection validation :query:`$jsonSchema`
 requires encryption for a field, clients performing explicit (manual)
 field level encryption **must** 

source/reference/method/KeyVault.addKeyAlternateName.txt

@@ -1,3 +1,5 @@
+.. _keyvault-addkeyaltname-method:
+
 ==============================
 KeyVault.addKeyAlternateName()
 ==============================

source/reference/method/KeyVault.createKey.txt

@@ -1,3 +1,5 @@
+.. _keyvault-createkey-method:
+
 ====================
 KeyVault.createKey()
 ====================

source/reference/method/KeyVault.deleteKey.txt

@@ -1,3 +1,5 @@
+.. _keyvault-deletekey-method:
+
 ====================
 KeyVault.deleteKey()
 ====================

source/reference/method/KeyVault.getKey.txt

@@ -1,3 +1,5 @@
+.. _keyvault-getkey-method:
+
 =================
 KeyVault.getKey()
 =================

source/reference/method/KeyVault.getKeyByAltName.txt

@@ -1,3 +1,5 @@
+.. _keyvault-getkeybyaltname-method:
+
 ==========================
 KeyVault.getKeyByAltName()
 ==========================

source/reference/method/KeyVault.getKeys.txt

@@ -1,3 +1,5 @@
+.. _keyvault-getkeys-method:
+
 ==================
 KeyVault.getKeys()
 ==================