(DOCSP-23734) Rename Realm to App Services (#543)

zach-carr · web-flow · commit a415d847f03f · 2022-08-15T09:27:50.000-04:00
* (DOCSP-23734) Rename Realm to App Services
diff --git a/snooty.toml b/snooty.toml
@@ -23,6 +23,9 @@ toc_landing_pages = ["/installation", "/dashboards", "/data-sources",
 
 [constants]
 version = "v0.10.0"
+app-services = "App Services"
+atlas-app-services = "Atlas App Services"
+atlas-app-services-link = ":appservices:`Atlas App Services </>`"
 
 [substitutions]
 charts = "MongoDB Charts"
diff --git a/source/configure-auth-providers.txt b/source/configure-auth-providers.txt
@@ -32,20 +32,21 @@ Considerations
 
 - |charts-short| supports these authentication providers:
 
-  - :stitch:`Realm </authentication/>`
+  - :stitch:`Atlas App Services </authentication/>`
   - Google
   - Custom |jwt|
 
-Realm Providers
-~~~~~~~~~~~~~~~
+{+atlas-app-services+} Providers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-|charts-short| considers tokens from Realm providers valid if they:
+|charts-short| considers tokens from {+app-services+} providers valid if 
+they:
 
 - Are syntactically valid |jwt|\s.
 
 - Are issued by the relevant authority.
 
-- Match the Realm App ID you configure the provider to accept.
+- Match the {+app-services+} App ID you configure the provider to accept.
 
 Google Providers
 ~~~~~~~~~~~~~~~~
diff --git a/source/dashboard-refresh.txt b/source/dashboard-refresh.txt
@@ -158,8 +158,9 @@ on both the client and server.
     .. note::
 
        If your chart is embedded using
-       :ref:`Realm Authentication <stitch-sdk-tutorial>` and
-       :guilabel:`Fetch data using Realm App` is enabled in your
+       :ref:`Atlas App Services Authentication <stitch-sdk-tutorial>` 
+       and
+       :guilabel:`Fetch data using Atlas App Services` is enabled in your
        :ref:`Authentication Provider Settings
        <configure-auth-providers>`, your chart does not load data from
        the server cache. Your ``maxDataAge`` embedding parameter still
diff --git a/source/embed-chart-stitch-auth.txt b/source/embed-chart-stitch-auth.txt
@@ -1,8 +1,8 @@
 .. _stitch-sdk-tutorial:
 
-======================================
-Embed a Chart Authenticated with Realm
-======================================
+=====================================================
+Embed a Chart Authenticated with {+atlas-app-services+}
+=====================================================
 
 .. default-domain:: mongodb
 
@@ -12,32 +12,26 @@ Embed a Chart Authenticated with Realm
    :depth: 2
    :class: singlecol
 
-.. note::
-
-   For the purposes of this tutorial, the names ``Realm`` and ``Stitch``
-   are used interchangably. They both refer to the :stitch:`MongoDB platform
-   as a service </>`.
-
-:stitch:`MongoDB Realm </>` is a serverless platform that enables developers
+{+atlas-app-services-link+} is a serverless platform that enables developers
 to quickly build applications without having to set up server infrastructure.
-Realm offers several authentication options, including `Google OAuth
+{+app-services+} offers several authentication options, including `Google OAuth
 <https://developers.google.com/identity/protocols/oauth2>`__, `Facebook Login
 <https://developers.facebook.com/docs/facebook-login/>`__, and email/password.
-You can use the authentication mechanism from a Realm app to control data
-access for an embedded chart.
+You can use the authentication mechanism from an app service to control 
+data access for an embedded chart.
 
 This tutorial shows you how to: 
 
 - Enable authenticated embedding for a chart.
 - Use the Embedding SDK to embed a chart authenticated by a custom
-  :stitch:`Realm </>` provider.
-- Use your Realm app to control the data in your embedded chart.
+  {+atlas-app-services-link+} provider.
+- Use your app service to control the data in your embedded chart.
 
 .. note::
 
-   This tutorial does not cover creating a Realm app with authentication.
-   See the :stitch:`Realm documentation </tutorials/>` for app creation
-   tutorials.
+   This tutorial does not cover creating an app service with authentication.
+   See the :stitch:`Atlas App Services documentation </tutorials/>` for 
+   app creation tutorials.
 
 Prerequisites
 -------------
@@ -47,7 +41,7 @@ Prerequisites
   configure embedding authentication providers for your linked 
   |charts-short| instance.
 
-- You must have a chart which uses your Realm app's backing database as
+- You must have a chart which uses your app's backing database as
   its :ref:`data source <data-sources>`. For more information about creating
   a chart, see :ref:`Build Charts <build-charts>`.
 
@@ -61,8 +55,8 @@ Enable Authenticated Embedding for a Chart
 
 .. include:: /includes/steps/embed-chart-authenticated.rst
 
-Configure |charts-short| to use your Custom Realm Provider
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Configure |charts-short| to use your Custom {+atlas-app-services+} Provider
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. include:: /includes/steps/add-auth-stitch-tutorial.rst
 
@@ -74,18 +68,18 @@ to add an :ref:`embedded chart <embedding-charts-sdk>`.
 If not, proceed with the remaining steps to create a new app.
 
 MongoDB offers a pre-built example app that shows how to use the 
-Embedding SDK to display an embedded chart using Realm authentication.
+Embedding SDK to display an embedded chart using {+app-services+} authentication.
 
 Clone the :github:`GitHub repository
 </mongodb-js/charts-embed-sdk/tree/master/examples/charts/authenticated-realm>` and
-follow the instructions in the ``Readme`` file to begin using the app. You can
-run the app as-is, or you can customize it to use the chart you created
-earlier.
+follow the instructions in the ``Readme`` file to begin using the app. 
+You can run the app as-is, or you can customize it to use the chart you 
+created earlier.
 
 .. note::
 
-   The example app assumes that your Realm app uses email/password
-   authentication. If your Realm app uses another authentication mechanism,
+   The example app assumes that your app service uses email/password
+   authentication. If your app service uses another authentication mechanism,
    the example app will require additional customization.
 
 Customize the Node.js App
diff --git a/source/embedded-chart-error-codes.txt b/source/embedded-chart-error-codes.txt
@@ -151,5 +151,5 @@ Refer to the following table for more information on each error code.
    * - ``18``
      - Client ID doesn't match provider.
 
-     - This error occurs for Realm and Google authentication providers
+     - This error occurs for {+atlas-app-services+} and Google authentication providers
        if the token is valid but was issued for a different application.
diff --git a/source/embedding-tutorials.txt b/source/embedding-tutorials.txt
@@ -30,7 +30,7 @@ login credentials through an SSO provider.
   the rendering of embedded charts in an application.
 
 :ref:`stitch-sdk-tutorial`
-  Configure |charts-short| to use :stitch:`MongoDB Realm </>` to authorize
+  Configure |charts-short| to use {+atlas-app-services-link+} to authorize
   the rendering of embedded charts in an application.
 
 :ref:`jwt-sdk-tutorial`
diff --git a/source/filter-embedded-charts.txt b/source/filter-embedded-charts.txt
@@ -264,12 +264,12 @@ sensitive information.
 
 .. note:: 
 
-   If you use a Realm Authentication Provider, ``context.token`` 
-   contains the Realm 
+   If you use an {+atlas-app-services+} authentication provider, ``context.token`` 
+   contains the {+app-services+} 
    :atlas:`user object </app-services/authentication/user-objects/>` to 
    filter. For example, if you enable 
    :atlas:`Custom User Data </app-services/users/enable-custom-user-data/>` 
-   for Realm users, the user object is available in 
+   for {+app-services+} users, the user object is available in 
    ``context.token.custom_data``.
 
 To inject a filter specific to each user, in the 
diff --git a/source/get-started-embedding-sdk.txt b/source/get-started-embedding-sdk.txt
@@ -132,7 +132,7 @@ Create a Web App
                MongoDB offers :github:`examples of authenticated embedded dashboards </mongodb-js/charts-embed-sdk/tree/master/examples/dashboard/>`
                in the GitHub Repository. These examples show you how to use
                the Embedding SDK to authenticate an embedded dashboard using
-               :stitch:`MongoDB Realm </>`, Google, or |jwt| authentication
+               {+atlas-app-services-link+}, Google, or |jwt| authentication
                providers.
 
 Add Embedding Code to Your App
@@ -186,13 +186,12 @@ To learn how to install the Embedding SDK into your app, see
             Add the following code to your web app to execute where you 
             want your chart to render. The following example 
             :ref:`authenticates <configure-auth-providers>` with 
-            :stitch:`MongoDB Realm </>`.
+            {+atlas-app-services-link+}.
 
             .. note::
 
-               Replace the existing Realm App ID with your Realm App 
-               ID, which you can find on the left side of your Realm 
-               app UI. Replace the existing Charts Base URL and chart 
+               Replace the existing App ID with your App 
+               ID, which you can find in the {+atlas-app-services+} UI. Replace the existing Charts Base URL and chart 
                ID with the values for the chart that you want to 
                display. Your Charts Base URL and chart ID are visible 
                in the embedding options modal window. 
@@ -202,16 +201,16 @@ To learn how to install the Embedding SDK into your app, see
 
                import ChartsEmbedSDK from "@mongodb-js/charts-embed-dom";
 
-               // Needed only if you are using the Realm authentication provider
+               // Needed only if you are using the Atlas App Services authentication provider
                const client = Stitch.initializeAppClient(
-                 'realm-authentication-sample-eibkj', // ~REPLACE~ with your Realm App ID
+                 'authentication-sample-eibkj', // ~REPLACE~ with your App ID
                });
 
                const sdk = new ChartsEmbedSDK({
                  baseUrl: "https://charts.mongodb.com/charts-embedding-examples-wgffp", // ~REPLACE~ with the Base URL from your Embed Chart dialog.
                  getUserToken: () => getRealmUserToken(client),
                  // getUserToken is a callback to provide the auth token to the SDK. 
-                 // Use the getRealmUserToken helper when using the Realm auth provider. 
+                 // Use the getRealmUserToken helper when using the Atlas App Services auth provider. 
                  // If using Custom JWT or Google providers, provide your own code to retrieve the JWT
                });
 
@@ -267,13 +266,12 @@ To learn how to install the Embedding SDK into your app, see
             Add the following code to your web app to run it where you
             want your dashboard to render. The following example
             :ref:`authenticates <configure-auth-providers>` with 
-            :stitch:`MongoDB Realm </>`.
+            {+atlas-app-services-link+}.
 
             .. note::
 
-               Replace the existing Realm App ID with your Realm
-               App ID. You can find the Realm ID on the left side
-               of your Realm app UI. Replace the existing :guilabel:`Dashboards
+               Replace the existing App ID with your
+               App ID. You can find your App ID in the {+atlas-app-services+} UI. Replace the existing :guilabel:`Dashboards
                Base URL` and dashboard ID with the values for the
                dashboard that you want to display. Your :guilabel:`Dashboards Base URL`
                and dashboard ID are visible in the embedding options
@@ -284,16 +282,16 @@ To learn how to install the Embedding SDK into your app, see
 
                import ChartsEmbedSDK from "@mongodb-js/charts-embed-dom";
 
-               // Needed only if you are using the Realm authentication provider
+               // Needed only if you are using the Atlas App Services authentication provider
                const client = Stitch.initializeAppClient(
-                  'realm-authentication-sample-eibkj', // ~REPLACE~ with your Realm App ID
+                  'authentication-sample-eibkj', // ~REPLACE~ with your App ID
                });
 
                const sdk = new ChartsEmbedSDK({
                   baseUrl: "https://charts.mongodb.com/charts-embedding-examples-wgffp", // ~REPLACE~ with the Base URL from your Embed Dashboard dialog.
                   getUserToken: () => getRealmUserToken(client),
                   // getUserToken is a callback to provide the auth token to the SDK. 
-                  // Use the getRealmUserToken helper when using the Realm auth provider. 
+                  // Use the getRealmUserToken helper when using the Atlas App Services auth provider. 
                   // If using Custom JWT or Google providers, provide your own code to retrieve the JWT
                });
 
diff --git a/source/includes/list-table-auth-provider-options.rst b/source/includes/list-table-auth-provider-options.rst
@@ -19,7 +19,7 @@
 
            <prefix>.apps.googleusercontent.com
 
-    * - Realm
+    * - {+atlas-app-services+}
       - Provide the following values:
 
-        .. include:: /includes/list-table-realm-auth-provider-options.rst
+        .. include:: /includes/list-table-realm-auth-provider-options.rst
diff --git a/source/includes/list-table-realm-auth-provider-options.rst b/source/includes/list-table-realm-auth-provider-options.rst
@@ -7,28 +7,29 @@
     - Value
 
   * - Project
-    - Project that contains your Realm application.
+    - Project that contains your app service.
 
-  * - Realm App
-    - Realm app that's issuing the user token.
+  * - App Service
+    - App service that's issuing the user token.
 
-  * - Fetch data using Realm app (**Optional**)
+  * - Fetch data using {+atlas-app-services+} (**Optional**)
     - Toggle to enable |charts-short| to fetch user data and rules from 
-      a Realm Service.
+      an app service.
 
       If enabled, |charts-short| retrieves data from the service you
-      specify in the :guilabel:`Realm Service Name` field.
+      specify in the :guilabel:`App Service Name` field.
 
-      Enabling this option allows you to define rules in Realm to 
+      Enabling this option allows you to define rules in {+atlas-app-services+} to 
       control the data that |charts-short| displays for specific 
       collections or users.
 
       For more information, see :stitch:`Filter Incoming Queries 
-      </mongodb/filter-incoming-queries/>` in the Realm documentation.
+      </mongodb/filter-incoming-queries/>` in the {+app-services+} 
+      documentation.
 
-  * - Realm Service Name
-    - The name of the service in your Realm app that |charts-short| uses 
-      to retrieve the data for your chart.
+  * - App Service Name
+    - The name of the service in your app service that |charts-short| 
+      uses to retrieve the data for your chart.
 
       .. example::
 
diff --git a/source/includes/steps-add-auth-stitch-tutorial.yaml b/source/includes/steps-add-auth-stitch-tutorial.yaml
@@ -19,26 +19,26 @@ inherit:
 ---
 stepnum: 4
 ref: add-auth-jwt-provider
-title: From the :guilabel:`Provider` list, select :guilabel:`Realm`.
+title: From the :guilabel:`Provider` list, select :guilabel:`Atlas App Services`.
 ---
 stepnum: 5
 ref: add-auth-atlas-project
-title: From the :guilabel:`Realm Project` list, select the |cloud-svc| project that contains your Realm app.
+title: From the :guilabel:`Atlas Project` list, select the |cloud-svc| project that contains your app service.
 ---
 stepnum: 6
 ref: add-auth-realm-app
-title: From the :guilabel:`Realm App` list, select the Realm app to use for authentication.
+title: From the :guilabel:`App ID` list, select the app service to use for authentication.
 ---
 stepnum: 7
 ref: fetch-realm-data
-title: Set toggle switch for using Realm rules for data access.
+title: Set toggle switch for using {+atlas-app-services+} rules for data access.
 content: |
   In addition to authenticating users for embedded chart access, you can
-  perform fine-grained data access control with your Realm app's :stitch:`service
+  perform fine-grained data access control with your app service :stitch:`service
   rules </services/define-a-service-rule/>`. Set the toggle switch to
   :guilabel:`On` if you want to enable rule enforcement.
 
-  When this option is enabled, any Realm rules defined on collections will
+  When this option is enabled, any {+app-services+} rules defined on collections will
   be observed by |charts-short| when retrieving chart data. You can use this
   feature to restrict access to the data shown on your chart, including
   showing different subsets of data to different users, depending on their
@@ -48,24 +48,24 @@ content: |
 
      - This option assumes that the :ref:`data source <data-sources>` for
        this chart uses the same MongoDB database and collection as your
-       Realm app.
+       app service.
 
      - Using this option may have a performance impact, so you should leave
-       it off if you do not need to restrict data access based on Realm
-       rules.
+       it off if you do not need to restrict data access based on 
+       {+app-services+} rules.
 ---
 stepnum: 8
 ref: enter-realm-service-name
-title: Enter Realm service name
+title: Enter service name.
 content: |
-  Enter the name of the service in your Realm app that fetches data from
+  Enter the name of the service that fetches data from
   MongoDB. To find the name of your data service:
   
-  a. Navigate to your Realm app.
+  a. Navigate to your app service.
   
   #. Click :guilabel:`Clusters` in the sidebar navigation.
 
-  #. The service name is listed under :guilabel:`Stitch Service Name`.
+  #. The service name is listed under :guilabel:`App Service Name`.
 ---
 stepnum: 9
 ref: realm-auth-click-save
diff --git a/source/includes/steps-add-realm-auth-chart.yaml b/source/includes/steps-add-realm-auth-chart.yaml
diff --git a/source/includes/steps-customize-realm-auth-app.yaml b/source/includes/steps-customize-realm-auth-app.yaml
diff --git a/source/release-notes.txt b/source/release-notes.txt
