DOCSP-45045 removed new OM nested components (#528)

kyuan-mongodb · web-flow · commit 048667d4ea29 · 2024-11-13T15:42:43.000-05:00
diff --git a/source/includes/steps-enable-authentication-oidc-workforce.rst b/source/includes/steps-enable-authentication-oidc-workforce.rst
@@ -132,10 +132,8 @@
              - hyphens (``-``)
              - underscores (``_``)
 
-             .. note::
-
-                After saving the configuration, 
-                you can't edit the configuration name.
+             After saving the configuration, 
+             you can't edit the configuration name.
       
          * - :guilabel:`Issuer URI`
            - Required
diff --git a/source/includes/steps-enable-authentication-oidc-workload-azure.rst b/source/includes/steps-enable-authentication-oidc-workload-azure.rst
@@ -132,10 +132,8 @@
              - hyphens (``-``)
              - underscores (``_``)
 
-             .. note::
-
-                After saving the configuration, 
-                you can't edit the configuration name.
+             After saving the configuration, 
+             you can't edit the configuration name.
 
          * - :guilabel:`Issuer URI`
            - Required
diff --git a/source/includes/steps-enable-authentication-oidc-workload-gcp.rst b/source/includes/steps-enable-authentication-oidc-workload-gcp.rst
@@ -132,10 +132,8 @@
              - hyphens (``-``)
              - underscores (``_``)
 
-             .. note::
-
-                After saving the configuration, 
-                you can't edit the configuration name.
+             After saving the configuration, 
+             you can't edit the configuration name.
 
          * - :guilabel:`Issuer URI`
            - Required
diff --git a/source/includes/steps-register-oidc-application-azure-workforce.rst b/source/includes/steps-register-oidc-application-azure-workforce.rst
@@ -3,15 +3,15 @@
 
    .. step:: Register an application.
 
-      1. Navigate to :guilabel:`App registrations`.
+      a. Navigate to :guilabel:`App registrations`.
 
-         a. In your `Azure portal <https://portal.azure.com/>`__ account, search and click :guilabel:`Microsoft Entra ID`.
+         i. In your `Azure portal <https://portal.azure.com/>`__ account, search and click :guilabel:`Microsoft Entra ID`.
 
          #. In the :guilabel:`Manage` section of the left navigation, click :guilabel:`App registrations`.
                
-      2. Click :guilabel:`New registration`.
+      #. Click :guilabel:`New registration`.
 
-      3. Apply the following values.
+      #. Apply the following values.
 
          .. list-table::
             :header-rows: 1
@@ -30,71 +30,71 @@
               - | - :guilabel:`Public client/native (mobile & desktop)`
                 | - ``http://localhost:27097/redirect``
 
-      4. Click :guilabel:`Register`.
+      #. Click :guilabel:`Register`.
 
       To learn more about registering an application, see `Azure Documentation <https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app#register-an-application>`__.
 
    .. step:: Add a group claim.
 
-      1. Navigate to :guilabel:`Token Configuration`.
+      a. Navigate to :guilabel:`Token Configuration`.
 
          In the :guilabel:`Manage` section of the left navigation,
          click :guilabel:`Token Configuration`.
 
-      2. Click :guilabel:`Add groups claim`.
+      #. Click :guilabel:`Add groups claim`.
 
-      3. In the :guilabel:`Edit groups claim` modal, select :guilabel:`Security`.
+      #. In the :guilabel:`Edit groups claim` modal, select :guilabel:`Security`.
 
          What groups you select depend on the type of groups you configured
          in your Azure environment. You may need to select a different
          type of group to send the appropriate group information.
 
-      4. In the :guilabel:`Customize token properties by type` section, only select :guilabel:`Group ID`.
+      #. In the :guilabel:`Customize token properties by type` section, only select :guilabel:`Group ID`.
 
-      5. Click :guilabel:`Add`.
+      #. Click :guilabel:`Add`.
 
       To learn more about adding a group claim, see :azure:`Azure Documentation </active-directory/hybrid/connect/how-to-connect-fed-group-claims>`.
 
    .. step:: Add a user identifier claim to the access token.
 
-      1. Click :guilabel:`Add optional claim`.
+      a. Click :guilabel:`Add optional claim`.
 
-      2. In the :guilabel:`Add optional claim` modal, select :guilabel:`Access`.
+      #. In the :guilabel:`Add optional claim` modal, select :guilabel:`Access`.
                
-      3. Select a claim that carries a user identifier that you can
+      #. Select a claim that carries a user identifier that you can
          refer to in MongoDB access logs such as an email.
 
          You can use the :abbr:`UPN (UserPrincipalName)` claim to identify users with their email address.
                
-      4. Click :guilabel:`Add`.
+      #. Click :guilabel:`Add`.
                
-      5. In the :guilabel:`Microsoft Graph Permissions` note, check the box, and click :guilabel:`Add`.
+      #. In the :guilabel:`Microsoft Graph Permissions` note, check the box, and click :guilabel:`Add`.
 
       To learn more, see :azure:`Azure Documentation </active-directory/develop/optional-claims>`.
 
    .. step:: Update the manifest.
 
-      1. In the :guilabel:`Manage` section of the left navigation, click :guilabel:`Manifest`.
+      a. In the :guilabel:`Manage` section of the left navigation, click :guilabel:`Manifest`.
 
-      2. Update the :guilabel:`accessTokenAcceptedVersion` from ``null`` to ``2``.
+      #. Update the :guilabel:`accessTokenAcceptedVersion` from ``null`` to ``2``.
 
          The number ``2`` represents Version 2 of Microsoft's access
          tokens. Other applications can use this as a signed
          attestation of the Active Directory-managed user's identity.
          Version 2 ensures that the token is a JSON Web Token that
          MongoDB understands.
                
-      3. Click :guilabel:`Save`.
+      #. Click :guilabel:`Save`.
 
       To learn more about adding an optional claim, see :azure:`Azure Documentation </active-directory/develop/reference-app-manifest>`.
 
    .. step:: Remember metadata.
 
-      1. In the left navigation, click :guilabel:`Overview`.
+      a. In the left navigation, click :guilabel:`Overview`.
                
          Copy the :guilabel:`Application (client) ID` value.
        
-      2. In the top navigation, click :guilabel:`Endpoints`.
+      #. In the top navigation, click :guilabel:`Endpoints`.
                   
          Copy the :guilabel:`OpenID Connect metadata document` value 
          without the ``/.well-known/openid-configuration`` part.
diff --git a/source/includes/steps-register-oidc-application-azure-workload.rst b/source/includes/steps-register-oidc-application-azure-workload.rst
@@ -3,15 +3,15 @@
 
    .. step:: Register an application.
 
-      1. Navigate to :guilabel:`App registrations`.
+      a. Navigate to :guilabel:`App registrations`.
 
-         a. In your `Azure portal <https://portal.azure.com/>`__ account, search and click :guilabel:`Microsoft Entra ID`.
+         i. In your `Azure portal <https://portal.azure.com/>`__ account, search and click :guilabel:`Microsoft Entra ID`.
 
-         b. In the :guilabel:`Manage` section of the left navigation, click :guilabel:`App registrations`.
+         #. In the :guilabel:`Manage` section of the left navigation, click :guilabel:`App registrations`.
      
-      2. Click :guilabel:`New registration`.
+      #. Click :guilabel:`New registration`.
 
-      3. Apply the following values.
+      #. Apply the following values.
 
          .. list-table::
             :header-rows: 1
@@ -38,61 +38,62 @@
       instead, you can set groups claim in your application registration 
       with below steps.
 
-      1. Navigate to :guilabel:`Token Configuration`.
+      a. Navigate to :guilabel:`Token Configuration`.
 
          In the :guilabel:`Manage` section of the left navigation,
          click :guilabel:`Token Configuration`.
 
-      2. Click :guilabel:`Add groups claim`.
+      #. Click :guilabel:`Add groups claim`.
 
-      3. In the :guilabel:`Edit groups claim` modal, select :guilabel:`Security`.
+      #. In the :guilabel:`Edit groups claim` modal, select
+         :guilabel:`Security`.
 
          What groups you select depend on the type of groups you configured
          in your Azure environment. You may need to select a different
          type of group to send the appropriate group information.
 
-      4. In the :guilabel:`Customize token properties by type` section, ensure that you only select :guilabel:`Group ID`.
+      #. In the :guilabel:`Customize token properties by type` section, ensure that you only select :guilabel:`Group ID`.
 
          When you select :guilabel:`Group Id`, Azure sends the
          security group's Object ID.
 
-      5. Click :guilabel:`Add`.
+      #. Click :guilabel:`Add`.
 
          To learn more about adding a group claim, see `Azure Documentation <https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-fed-group-claims>`__.
 
    .. step:: Enable an Application ID URI.
 
-      1. Navigate to :guilabel:`Expose an API` 
+      a. Navigate to :guilabel:`Expose an API` 
          in the left sidebar and enable Application ID URI.
       
-      2. Enable an Application ID URI.
+      #. Enable an Application ID URI.
        
-         a. Keep the default Application ID URI assigned by Azure, 
+         i. Keep the default Application ID URI assigned by Azure, 
             which is ``<application_client_id>``. Copy and store this value, 
             as |mms| and all MongoDB drivers require this value 
             for |workload| configuration.
 
    .. step:: Update the manifest.
 
-      1. In the :guilabel:`Manage` section of the left navigation, click :guilabel:`Manifest`.
+      a. In the :guilabel:`Manage` section of the left navigation, click :guilabel:`Manifest`.
 
-      2. Update the :guilabel:`accessTokenAcceptedVersion` from ``null`` to ``2``.
+      #. Update the :guilabel:`accessTokenAcceptedVersion` from ``null`` to ``2``.
 
          The number ``2`` represents Version 2 of Microsoft's access
          tokens. Other applications can use this as a signed
          attestation of the Active Directory-managed user's identity.
          Version 2 ensures that the token is a JSON Web Token that
          MongoDB understands.
         
-      3. Click :guilabel:`Save`.
+      #. Click :guilabel:`Save`.
 
       To learn more about adding an optional claim, see `Azure Documentation <https://learn.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest>`__.
 
    .. step:: Remember metadata.
 
-      1. In the left navigation, click :guilabel:`Overview`.
+      a. In the left navigation, click :guilabel:`Overview`.
         
-      2. In the top navigation, click :guilabel:`Endpoints`.
+      #. In the top navigation, click :guilabel:`Endpoints`.
            
          Copy the :guilabel:`OpenID Connect metadata document` value 
          without the ``/.well-known/openid-configuration`` part.
