(DOCSP-20913): mongocli auth login (#671)

* (DOCSP-20913): mongocli auth login

* Update quickstarts

* yaml fix

* Tech review

* copy review

* Ensure submodule is on v1.23.0

Author: melissamahoney-mongodb

source/configure.txt

@@ -22,40 +22,13 @@ Configure the {+mcli+}
 
 You can define the settings that the {+mcli+} uses to interact with
 MongoDB services like |service|, |cloud-short|, and |onprem| by using
-the :ref:`mongocli-config` command. The first time you run this
-command, the {+mcli+} creates a :ref:`configuration file
-<mcli-config-file>` called ``mongocli.toml`` to store your settings. 
-
-Prerequisites
--------------
-
-To configure the {+mcli+}:
-
-- Add your |ipaddr| or |cidr| block to the |api| whitelist for your
-  MongoDB service.
-- Generate a |svc-api-key| if you don't already have one.
-  
-  .. note::
-
-     |svc-api-key|\s are role-based. Different roles have different
-     privileges and capabilities, and some {+mcli+} commands are available
-     to some roles but not others. Be sure that the roles assigned to
-     your |svc-api-key| are appropriate for the commands you intend to
-     use.
-
-To learn more about generating a |svc-api-key| for
-your MongoDB service, see the following documentation:
-
-- :atlas:`Atlas API Access </configure-api-access>`
-- :cloudmgr:`Cloud Manager API Access </tutorial/configure-public-api-access>`
-- :opsmgr:`Ops Manager API Acess </tutorial/configure-public-api-access>`
+the :ref:`mongocli-auth-login` or :ref:`mongocli-config` commands.
+The first time you run one of these commands, the {+mcli+} creates a :ref:`configuration file
+<mcli-config-file>` called ``mongocli.toml`` to store your settings.
 
 Procedure
 ---------
 
-The :ref:`mongocli-config` command varies slightly depending on the
-MongoDB service for which you want to configure the {+mcli+}.
-
 .. tabs::
 
    .. tab:: Atlas

source/includes/admonitions/note-api-key-roles.rst

@@ -0,0 +1,7 @@
+.. note::
+
+   |svc-api-key|\s are role-based. Different roles have different
+   privileges and capabilities, and some {+mcli+} commands are available
+   to some roles but not others. Be sure to assign roles to
+   your |svc-api-key| that are appropriate for the commands you intend to
+   use.

source/includes/steps-configure-mcli-atlas.yaml

@@ -1,27 +1,25 @@
 stepnum: 1
 source:
   file: steps-configure-mcli.yaml
-  ref: create-profile
+  ref: auth-login
 replacement:
+  service: "|service|"
   serviceOption: ""
 ---
 stepnum: 2
 source:
   file: steps-configure-mcli.yaml
-  ref: enter-api-key
-replacement:
-  apiKeys: ":atlas:`Programmatic API Key </configure-api-access>`"
-  service: "|service|"
+  ref: auth-create-profile
 ---
 stepnum: 3
 source:
   file: steps-configure-mcli.yaml
-  ref: enter-orgid-atlas-cm
+  ref: auth-enter-orgid-atlas-cm
 ---
 stepnum: 4
 source:
   file: steps-configure-mcli.yaml
-  ref: enter-projectid
+  ref: auth-enter-projectid
 ---
 stepnum: 5
 source:
@@ -34,6 +32,14 @@ source:
   ref: enter-mongo-shell-path
 ---
 stepnum: 7
+source:
+  file: steps-configure-mcli.yaml
+  ref: add-api-keys
+replacement:
+  service: "|service|"
+  api-access-url: ":atlas:`Programmatic API Key </configure-api-access>`"
+---
+stepnum: 8
 source:
   file: steps-configure-mcli.yaml
   ref: verify-profile

source/includes/steps-configure-mcli-cm.yaml

@@ -1,27 +1,25 @@
 stepnum: 1
 source:
   file: steps-configure-mcli.yaml
-  ref: create-profile
+  ref: auth-login
 replacement:
-  serviceOption: "--service cloud-manager"
+  service: "|cloud|"
+  serviceOption: "--cm"
 ---
 stepnum: 2
 source:
   file: steps-configure-mcli.yaml
-  ref: enter-api-key
-replacement:
-  apiKeys: ":cloudmgr:`API keys </tutorial/configure-public-api-access>`"
-  service: "|cloud|"
+  ref: auth-create-profile
 ---
 stepnum: 3
 source:
   file: steps-configure-mcli.yaml
-  ref: enter-orgid-atlas-cm
+  ref: auth-enter-orgid-atlas-cm
 ---
 stepnum: 4
 source:
   file: steps-configure-mcli.yaml
-  ref: enter-projectid
+  ref: auth-enter-projectid
 ---
 stepnum: 5
 source:
@@ -34,6 +32,14 @@ source:
   ref: enter-mongo-shell-path
 ---
 stepnum: 7
+source:
+  file: steps-configure-mcli.yaml
+  ref: add-api-keys
+replacement:
+  service: "|cloud|"
+  api-access-url: ":cloudmgr:`API keys </tutorial/configure-public-api-access>`"
+---
+stepnum: 8
 source:
   file: steps-configure-mcli.yaml
   ref: verify-profile

source/includes/steps-configure-mcli-om.yaml

@@ -1,44 +1,52 @@
 stepnum: 1
+source:
+  file: steps-configure-mcli.yaml
+  ref: config-prereqs
+replacement:
+  service: "|onprem|"
+  api-access-url: ":opsmgr:`Ops Manager API Access </tutorial/configure-public-api-access>`"
+---
+stepnum: 2
 source:
   file: steps-configure-mcli.yaml
   ref: create-profile
 replacement:
   serviceOption: "--service ops-manager"
 ---
-stepnum: 2
+stepnum: 3
 source:
   file: steps-configure-mcli.yaml
   ref: enter-base-url
 ---
-stepnum: 3
+stepnum: 4
 source:
   file: steps-configure-mcli.yaml
   ref: enter-api-key
 replacement:
   apiKeys: ":opsmgr:`API keys </tutorial/configure-public-api-access>`"
   service: "|onprem|"
 ---
-stepnum: 4
+stepnum: 5
 source:
   file: steps-configure-mcli.yaml
   ref: enter-orgid-om
 ---
-stepnum: 5
+stepnum: 6
 source:
   file: steps-configure-mcli.yaml
   ref: enter-projectid
 ---
-stepnum: 6
+stepnum: 7
 source:
   file: steps-configure-mcli.yaml
   ref: enter-fileformat
 ---
-stepnum: 7
+stepnum: 8
 source:
   file: steps-configure-mcli.yaml
   ref: enter-mongo-shell-path
 ---
-stepnum: 8
+stepnum: 9
 source:
   file: steps-configure-mcli.yaml
   ref: verify-profile